Tracking proximities of devices and/or objects

ABSTRACT

Disclosed herein are system, apparatus, article of manufacture, method, and/or computer program product embodiments for tracking proximities of devices and/or objects. In one embodiment, the system operates by determining whether a plurality of devices of a tethered segment are inside or outside a predefined area. The system also operates by determining that a first device of the plurality of devices is outside of the predefined area based at least partially on the determination of whether the plurality of devices are inside or outside the predefined area. The system further operates by transmitting at least one alert notification to at least one device based at least partially on the determination that the first device is outside the predefined area, wherein the alert notification identifies the first device outside the predefined area.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. Non-Provisional patentapplication Ser. No. 16/281,901, titled “TRACKING PROXIMITIES OF DEVICESAND/OR OBJECTS,” filed Feb. 21, 2019, which is a continuation of U.S.Non-Provisional patent application Ser. No. 15/802,719, titled “TRACKINGPROXIMITIES OF DEVICES AND/OR OBJECTS,” filed Nov. 3, 2017. All of theabove applications are herein incorporated by reference in theirentireties.

BACKGROUND Field

This disclosure is generally directed to tracking proximities of devicesand/or objects.

Background

From work place entry devices to vehicle entry devices and otherpersonal effects such as wallets and mobile phones, the number ofdevices and objects that users may be required to carry with them hasincreased over time. Coupled with numerous responsibilities that theusers may be tasked to handle under strict timelines, being mindful tocarrying these objects and devices has also increased importance.Oftentimes, the consequences of forgetting or misplacing any one ofthese devices (e.g., entry devices) or objects (e.g., wallet) couldresult in substantial decrease in productivity. Accordingly, a solutionis needed to track the proximity of various devices and objects.

SUMMARY

Provided herein are system, apparatus, article of manufacture, methodand/or computer program product embodiments, and/or combinations andsub-combinations thereof, for tracking proximities of devices and/orobjects.

An embodiment includes a computer implemented method for trackingproximities of devices and/or objects. The method may operate bydetermining whether a plurality of devices of a tethered segment iswithin a predefined area and determining that a first device and asecond device of the plurality of devices are inside the predefinedarea. The method may also operate by predicting whether the first devicewill move outside the predefined area without the second device. Themethod may further operate by transmitting at least one alertnotification to at least one device based at least partially on theprediction that the first device will move outside the predefined areawithout the second device, wherein the alert notification identifies thefirst device and indicates that the first device is predicted to moveoutside the predefined area without the second device.

Another embodiment includes a tracking device for tracking proximitiesof utility devices and/or objects. The tracking device may include atleast one processor and a memory coupled to the at least one processorand configured to determine whether a plurality of devices of a tetheredsegment are inside or outside a predefined area and determine that afirst device of the plurality of devices is outside of the predefinedarea based at least partially on the determination of whether theplurality of devices are inside or outside the predefined area. The atleast one processor may be further configured to transmit at least onealert notification to at least one device based at least partially onthe determination that the first device is outside the predefined area,wherein the alert notification identifies the first device outside thepredefined area.

A further embodiment includes a tangible computer-readable device havinginstructions stored thereon that, when executed by at least onecomputing device, causes the at least one computing device to performoperations. The operations may include, without limitation, determiningwhether a plurality of devices of a tethered segment are inside oroutside a predefined area and determining that a first device of theplurality of devices is outside of the predefined area based at leastpartially on the determination of whether the plurality of devices areinside or outside the predefined area. The operations may furtherinclude, without limitation, transmitting at least one alertnotification to at least one device based at least partially on thedetermination that the first device is outside the predefined area,wherein the alert notification identifies the first device outside thepredefined area.

BRIEF DESCRIPTION OF THE FIGURES

The accompanying drawings are incorporated herein and form a part of thespecification.

FIG. 1 illustrates a mobile sensory system for tracking devices and/orobjects according to some embodiments.

FIG. 2 illustrates components of a mobile device according to someembodiments.

FIG. 3 illustrates components of a mobile sensory device according tosome embodiments.

FIG. 4 illustrates components of an audio responsive electronic device(ARED) according to some embodiments.

FIGS. 5A-5C illustrate example information stored in a device datastoreaccording to some embodiments.

FIGS. 6A-6B illustrate example interactions between an ARED, mobilesensory devices, and a mobile device according to some embodiments.

FIGS. 7A-7B illustrate example interactions between mobile sensorydevices and a mobile device according to some embodiments.

FIGS. 8A-8C illustrate example processing operations that may beperformed by a mobile device and/or a mobile sensory device according tosome embodiments.

FIGS. 9A-9E illustrate example processing operations performed by amobile device and/or an ARED according to some embodiments.

FIG. 10 is an example computer system useful for implementing variousembodiments of this disclosure.

Like reference numerals refer to corresponding parts throughout theseveral views of the drawings. Additionally, generally, the left-mostdigit(s) of a reference number identifies the drawing in which thereference number first appears. Furthermore, one or more designators tothe right of a reference number such as, for example, “a” and “b” and“c” and other similar designators are intended to be variablesrepresenting any positive integer. Thus, for example, if animplementation sets a value for a=4, then a set of elements 104-a mayinclude elements 114-1, 114-2, 114-3, and 114-4.

DETAILED DESCRIPTION

FIG. 1 illustrates a block diagram according to an example embodiment ofa mobile sensory system 100. In particular, the mobile sensory system100 may include one or more utility objects 112-a, one or more mobilesensory devices 114-b, a mobile device 102, and optionally, an audioresponsive electronic device (ARED) 106. In an embodiment, the ARED 106may be operatively coupled to a power source 108, which may be anexternal power source configured to provide continuous power to the ARED106.

In an embodiment, the one or more mobile sensory devices 114-b, mobiledevice 102, and optionally, ARED 106 may all be communicatively and/oroperatively coupled together via network 150. In various embodiments,the network 150 may include, without limitation, a computer and/ortelecommunications network which may enable coupled and/orinterconnected systems and/or devices to communicate information betweenand among each other. In various embodiments, the network 150 maygenerally include, without limitation, intranet, extranet, Internet,and/or any other local, regional, global telecommunications network. Insome embodiments, the network 150 may be limited to a local area networksuch as, for example, a local area network in a business office and/orhome residence.

In an embodiment, the utility objects 112-a may generally represent anyphysical item, objects, and/or personal effects, that a user would liketo keep track of their physical location, maintain physical proximitywith and/or receive one or more notifications when the user may haveforgotten to bring these utility objects 112-a with him/her. Forexample, utility objects may include, without limitation, wallets, keys,laptops, tablets, mobile phones, and/or any other physical objects thata user may want to track their physical location of. Additionally, inembodiments where utility objects 112-a are electronic devices, thesedevices may also be communicatively and/or operatively coupled tonetwork 150.

In an embodiment and to keep track of these various utility objects112-a, a user may physically couple a mobile sensory device such asmobile sensory device 114-1, 114-2, 114-3 . . . 114-b to the one or moreutility objects 112-a. The physical coupling may include, withoutlimitation, hook and loop fasteners (e.g., Velcro, etc.), physicalclips, negative fluid pressure attachment devices (e.g., suctionpads/cups, etc.), temporary and/or permanent adhesives, and/or any othercoupling that can physically bind a mobile sensory device to variousutility objects 112-a.

In an embodiment and to track of these various utility objects 112-a,the mobile sensory devices 114-b may be generally configured to performpassive tracking operations which generally enable a designated leaddevice or an ARED to perform active tracking operations. These passivetracking operations may include, without limitation: (1) detect physicalmotion or movement (e.g., acceleration, deceleration, angular rotation,etc.); (2) transmit device activity information corresponding to thedetected physical motion or movement to the ARED and/or designated leaddevice (e.g., mobile device 102 which may be designated as the leadmobile device); (3) receive alert notification from a designated leaddevice and/or ARED indicating that at least one mobile sensory device ormobile may be leaving the physical proximity; and/or (4) activating atleast one feedback, in response to the alert notification.

Furthermore, in addition to transmitting device activity informationupon detection of physical motion or movement, the mobile sensorydevices 114-b may also be configured to provide device activityinformation upon request. Thus, in an embodiment the mobile sensorydevices 114-b may also be generally configured to: (1) receive a requestfor device activity information (i.e., device activity request) from adesignated lead device and/or an ARED; and/or (2) transmit a deviceactivity response to the mobile device and/or ARED, in response to thedevice activity request.

In an embodiment, the mobile device 102 may be generally configured tooperate as a designated lead device (i.e., a designated lead mobiledevice) or as a follower device (i.e. a follower mobile device). As afollower mobile device, the follower mobile device (e.g., mobile device102) may be configured to perform passive tracking operations in asimilar manner as the one or more mobile sensory devices 114-b discussedabove and herein. This enables the follower mobile device 102 to betracked in a similar manner to a mobile sensory device withoutphysically attaching a mobile sensory device to the follower mobiledevice.

As a designated lead mobile device, the mobile device 102 may performactive tracking operations that actively assist in tracking variousutility objects 112-b and/or follower mobile devices, when designatedlead mobile device is not within predefined area of the ARED 106. Theseactive tracking operations may include, without limitation, determiningwhether a mobile sensory device and/or another mobile device in apredefined set of devices for a user (i.e., a tethered segment furtherdiscussed below) is and/or will remain inside a predefined area of thedesigned lead mobile device (e.g., within a physical proximity of adesigned lead mobile device 102).

In some embodiments, the predefined area of the designated lead mobiledevice may include a limited geographical area surrounding the designedlead mobile device. The limited geographical area surrounding orotherwise enclosing the designed lead mobile device may be defined, forexample, by the wireless communications range between the designed leadmobile device and various devices. In some embodiments, the designedlead mobile device may also be substantially near the center of thelimited geographical area. Similarly and in some embodiments, thepredefined area of the ARED may include a limited geographical areasurrounding or otherwise enclosing the ARED. The limited geographicalarea may be defined by the wireless communications range between theARED and various devices. However, this disclosure is not limited tothis example. Other techniques and technologies for establishing thelimited geographical area may also fall within the scope and spirit ofthis disclosure.

Based on these determinations, the designated lead mobile device maytransmit an alert notification to at least one device (e.g., mobilesensory device and/or a follower mobile device). The alert notificationmay indicate that the designed lead mobile device 102 has determinedthat a device is not inside the limited geographical area and/orpredicted to not remain in the limited geographical area. In someembodiments, the alert notification may be transmitted to only deviceswithin the predefined set of devices for the user, or may be transmittedto other devices previously identified by the user. The alertnotification may also identify the device that is not within the limitedgeographical area.

As the designated lead mobile device 102 that is actively assisting intracking various devices, the lead mobile device 102 may be generallyconfigured to: (1) receive device activity information from followermobile devices (not shown) and/or follower mobile sensory devices 114-b;and (2) update device activity information stored for each device in adevice datastore based on the received device activity information.

Additionally, for each tethered segment, the designated lead mobiledevice 102 may be configured to: (1) determine whether all the followerdevices are within physical proximity of the designated lead mobiledevice 102; and/or (2) predict whether all the follower devices willremain within or leave the physical proximity of the designated leadmobile device 102. The designated lead mobile device 102 may be furtherconfigured to: (1) transmit at least one alert notification to at leastone of a follower device; and/or (2) activate at least one feedback tonotify the user, when the designated lead mobile device 102 determinesthat a follower device may not be within physical proximity of thedesignated lead mobile device 102 and/or predicts that a follower devicewill not remain within physical proximity of the designated lead mobiledevice 102.

In an embodiment where an ARED 106 is optionally available in a localarea network, the ARED 106 may be configured to perform similar activetracking operations as a designated lead mobile device discussed aboveand herein. In those embodiments, a designed lead mobile device (e.g.,designated lead mobile device 102) within the limited geographical areaof the ARED 106 (e.g., within physical proximity of the ARED 106) may beconfigured to perform functions of a follower mobile device. This allowsthe ARED 106 to actively track mobile sensory devices and/or mobiledevices rather than the designed lead mobile device performing activetracking operations in order to reduce power consumption of the designedlead mobile device.

In an embodiment and to actively track mobile sensory devices and/ormobile devices, the operations ARED 106 may perform active trackingoperations similarly discussed above and herein with respect to thedesigned lead mobile device 102. These active tracking operations forthe ARED 106 may include, without limitation: (1) determining that afirst mobile sensory device and/or first mobile device in a predefinedset of devices for a user (i.e., a tethered segment further discussedbelow) is not and/or will not remain inside a limited geographical areasurrounding the ARED 106 (e.g., within a physical proximity of the ARED106); and (2) determining that a second mobile sensory device and/orsecond mobile device in the same predefined set of devices for a user isand/or will remain inside a limited geographical area surrounding theARED 106.

Based on these determinations, the active tracking operations mayfurther include, without limitation, transmitting an alert notificationto at least one device (e.g., mobile sensory device and/or a followermobile device). The alert notification may indicate that the ARED 106has determined that the first device has left or will leave thegeographical area while the second device remains within thegeographical area. In some embodiments, the alert notification may betransmitted to only devices within the predefined set of devices for theuser. The alert notification may also identify the device that is notwithin the limited geographical area, i.e., identify the first device,which is leaving the limited geographical area of the ARED 106.

It should be understood that, while the ARED 106 and mobile devices aredescribed herein as performing certain functions and/or operations,those functions and/or operations may instead be performed by othermonitoring devices, components and/or processes.

In an embodiment and to ensure that alert notifications are given to aspecific user regarding utility objects 112-a that only the specificuser care about, each mobile device (e.g., mobile device 102) and mobilesensory device (e.g., mobile sensory device 114-b) may be associatedwith tethered segments 118-d. Thus, each tethered segment (e.g.,tethered segment 118-1, 118-2, etc.) may include one or more tethereddevices such as one or more mobile devices and/or one or more mobilesensory devices.

In an embodiment and for any tethered devices that are within the sametethered segment 118-1, at least one tethered device may be configuredto provide feedback (e.g., a visual feedback, an auditory feedback,haptic feedback, text message, email message, etc.) to alert a user. Forexample, the at least one tethered device may be configured to providefeedback, when at least one tethered device within the tethered segment(e.g., tethered segment 118-1) is determined and/or otherwise predictedto not be within physical proximity of another device (e.g., mobiledevice 102, a mobile sensory device 112-1, 112-2, etc.) in the sametethered segment (e.g., tethered segment 118-1).

FIG. 2 illustrates a block diagram of an example embodiment of themobile device 102. It is to be appreciated that while FIG. 2 illustratesone example embodiment of the mobile device 102, the example embodimentis not limited to this context.

In an embodiment, the mobile device 102 may be generally arranged toprovide mobile computing and/or mobile communications and may include,but are not limited to, memory 270, communications component 274, motioncomponent 276, and orientation component 278, acoustic input/outputcomponent 280, haptic component 282, mobile processor component 284,touch sensitive display component 286, location component 288, internalpower component 290, where each of the components and memory 270 may beoperatively connected via interconnect 292.

In an embodiment, the memory 270 may be generally arranged to storeinformation in volatile and/or nonvolatile memory, which may include,but is not limited to, read-only memory (ROM), random-access memory(RAM), dynamic RAM (DRAM), Double-Data-Rate DRAM (DDRAM), synchronousDRAM (SDRAM), static RAM (SRAM), programmable ROM (PROM), erasableprogrammable ROM (EPROM), electrically erasable programmable ROM(EEPROM) flash memory, polymer memory such as ferroelectric polymermemory, ovonic memory, phase change or ferroelectric memory,silicon-oxide-nitride-oxide-silicon (SONOS) memory, solid state memorydevices (e.g., USB memory, solid state drives SSD, etc.), and/or anyother type of storage media configured for storing information.

In an embodiment, the memory 270 may include instruction informationarranged for execution by the mobile processor component 284. In thatembodiment, the instruction information may be representative of atleast one operating system 272, one or more applications, which mayinclude, but are not limited to, mobile device control application 212.In an embodiment, the memory 270 may further include device datastore250 which may be configured to store device configuration informationfurther illustrated in FIG. 5A, device activity information furtherillustrated in FIG. 5B, and device user information further illustratedin FIG. 5C.

In an embodiment, the mobile operating system 272 may include, withoutlimitation, mobile operating systems (e.g., Apple®, iOS®, Google®Android®, Microsoft® Windows Phone®, Microsoft® Windows®, etc.) generalarranged to manage hardware resources (e.g., one or more components ofthe mobile device 102, etc.) and/or software resources (e.g., one ormore applications of the mobile device 102, etc.).

In an embodiment, the communications component 274 may be generallyarranged to enable the mobile device 102 to communicate, directly and/orindirectly, with various devices (e.g., mobile sensory devices 114-b,ARED 106, etc.) in the mobile sensory system 100. The communicationscomponent 274 may include, among other elements, a radio frequencycircuit (not shown) configured for encoding and/or decoding informationand receiving and/or transmitting the encoded information as radiosignals in frequencies consistent with the one or more wirelesscommunications standards (e.g., Bluetooth, Wireless IEEE 802.11, WiMAXIEEE 802.16, Global Systems for Mobile Communications (GSM), EnhancedData Rates for GSM Evolution (EDGE), Long Term Evolution (LTE),Bluetooth standards, Near Field Communications (NFC) standards, etc.).

In an embodiment, the motion component 276 may be generally arranged todetect motion of the mobile device 102 in one or more axes. The motioncomponent 276 may include, among other elements, motion sensor (e.g.,accelerometer, micro gyroscope, etc.) to convert physical motionsapplied to or exerted on the mobile device 118-1 into motioninformation.

In an embodiment, the orientation component 278 may be generallyarranged to detect magnetic fields for measuring the strength ofmagnetic fields surrounding the mobile device 102. The orientationcomponent 278 may include, among other elements, magnetic sensor (e.g.,magnetometer, magnetoresistive permalloy sensor, etc.) to convertmagnetic field applied to or exerted on the mobile device 102 intoorientation information, which may identify a number of degrees from areference orientation the mobile device 102 is oriented or otherwisepointed.

In an embodiment, the acoustic input/output (I/O) component 280 may begenerally arranged for converting sound, vibrations, or any othermechanical waves received by the mobile device 102 into digital orelectronic signals representative of acoustic input informationutilizing one or more acoustic sensors (e.g., microphones, etc.), whichmay be located or positioned on or within the housing, case, orenclosure of the mobile device 102 to form an microphone array.Additionally, the acoustic I/O component 280 may be further arranged toreceive acoustic output information and convert the received acousticoutput information into electronic signals to output sound, vibrations,or any other mechanical waves utilizing the one or more electroacoustictransducers (e.g., speakers, etc.) which may be located or positioned onor within the housing, case, or enclosure of the mobile device 102.Additionally or alternatively, the acoustic output information and/orthe covered electronic signals may be provided to one or moreelectroacoustic transducers (e.g., speakers, etc.) operatively coupledto the mobile device 102 via wired and/or wireless connections.

In an embodiment, the haptic component 282 may be generally arranged toprovide tactile feedback with varying strength and/or frequency withrespect to time through the housing, case, or enclosure of the mobiledevice 102. Moreover, the haptic component 282 may include, among otherelements, a vibration circuit (e.g., an oscillating motor, vibratingmotor, etc.) arranged to receive haptic output information and convertthe received haptic output information to mechanical vibrationsrepresentative of tactile feedback.

In an embodiment, the mobile processor component 284 may be generallyarranged to execute instruction information including one or moreinstructions. In an embodiment, the processor component 284 may be amobile processor component or system-on-chip (SoC) processor componentwhich may comprise, among other elements, processor circuit, which mayinclude, but is not limited to, at least one set of electronic circuitsarranged to execute one or more instructions. Examples of mobileprocessor components 284 may include, but is not limited to, Qualcomm®Snapdragon®, Nvidia® Tegra®, Intel® Atom®, Samsung® Exynos, Apple® A7®,Apple® A8®, or any other type of mobile processor(s) arranged to executethe instruction information including the one or more instructionsstored in memory 270.

In an embodiment, the touch sensitive display component 286 may begenerally arranged to receive and present visual display information,and provide touch input information based on detected touch based orcontact based input. Moreover, the touch sensitive display component 286may include, among other elements, display device (e.g., liquid-crystaldisplay, light-emitting diode display, organic light-emitting diodedisplay, etc.) for presenting the visual display information and touchsensor(s) (e.g., resistive touch sensor, capacitive touch sensor, etc.)associated with the display device 268 to detect and/or receive touch orcontact based input information associated with the display device ofthe mobile device 102. Additionally, the touch sensor(s) may beintegrated with the surface of the display device, so that a user'stouch or contact input may substantially correspond to the presentedvisual display information on the display device.

In an embodiment, the location component 288 may be generally arrangedto receive positioning signals representative of positioning informationand provide location information (e.g., approximate physical location ofthe mobile device 102) determined based at least partially on thereceived positioning information. Moreover, the location component 288may include, among other elements, positioning circuit (e.g., a globalpositioning system (GPS) receiver, etc.) arranged to determine thephysical location of the mobile device 102. In some embodiments, thelocation component 288 may be further arranged to communicate and/orinterface with the communications component 274 in order to providegreater accuracy and/or faster determination of the locationinformation.

In an embodiment, the internal power component 290 may be generallyarranged to provide power to the various components and the memory ofthe mobile device 102. In an embodiment, the internal power component290 may include and/or be operatively coupled to an internal and/orexternal battery configured to provide power to the various components(e.g., communications component 274, motion component 276, memory 270,etc.).

In an embodiment, the mobile device control application 212 may begenerally configured to perform active tracking operations that activelyassist in tracking of various utility objects 112-b and/or followermobile devices within a limited geographical area surrounding the mobiledevice 102, when the mobile device 102 is: (1) a designed lead mobiledevice; and (2) not within physical proximity of an ARED. Additionallyor alternatively, the mobile device control application 212 may also begenerally configured to perform passive tracking operations thatpassively assist in tracking of the mobile device 102 within a limitedgeographical area surrounding a designated lead mobile device or anARED, when the mobile device 102 is: (1) designated as a followerdevice; or (2) not within physical proximity of an ARED.

In an embodiment, the mobile device control application 212 may befurther configured to perform management operations that enablemodification and/or updates to device configuration information and/ordevice user information for various devices associated with a user ofthe mobile device 102 and/or ARED 106. To perform these operationsdiscussed above, the mobile device control application 212 may include,without limitation, management component 214, activity component 216,feedback component 218, and proximity component 220.

To perform the management operations, the management component 214 maybe generally configured to provide visual display informationrepresentative of one or more user interface (UI) views to the touchsensitive display component 286. Additionally, the management component214 may be generally configured to receive touch or contact based inputinformation corresponding to the one or more UI views to enable a userto: (1) add and/or remove one or more mobile sensory devices 114-aand/or mobile device 102 to one or more a tethered segments (e.g.,tethered segment 118-1, etc.); (2) assign or otherwise designate a leadand follower devices within the one or more a tethered segments (e.g.,tethered segment 118-1, etc.); (3) configure the activation of one ormore indicators associated with the mobile device 102 and/or mobilesensory devices 114-b in order to provide at least one feedback to theuser, when a mobile device 102 or a mobile sensory device leavesphysical proximity with respect to each other; and/or (4) associatecontact information with a user of the mobile sensory system 100.

In embodiments where the mobile device 102 is within the physicalproximity of an ARED 106 (e.g., operatively and/or communicativelycoupled to the ARED 106 in a local area network 150), the managementcomponent 214 may be generally configured to perform passive trackingoperations. In these embodiments, the management component 214 may beconfigured to communicate with the ARED 106 and provide device activityinformation generated by the activity component 216 to the ARED 106.Additionally, the management component 214 may also be generallyconfigured to receive alert notifications from ARED 106 indicating thatone or more devices within a tethered segment is not within physicalproximity of each other. In response to the alert notification, themobile device 102 may also be configured to provide auditory, haptic,and/or visual feedback to the user of the mobile device 102 based on thedevice configuration information indicating various types of feedbackenabled by the user.

In addition to or alternative to providing feedback directly to the uservia mobile device 102, the ARED 106 may also be configured to transmitemail messages and/or text messages to the user of the mobile device 102across various networks (e.g., Cellular Networks, Wide Area Networks(WAN), Virtual Private Networks (VPNs), Internet, etc.). Thus, in anembodiment, the ARED 106 may be operatively and communicatively coupledto one or more Mail Transfer Agents (e.g., mail servers)(not shown) andmay be further configured to transmit email messages to the user of themobile device 102 via the one or more Mail Transfer Agents.

Additionally or alternatively, the ARED 106 may also be operatively andcommunicatively coupled to one or more Short Messaging Service (SMS)servers (not shown) may be further configured to transmit text messagesto the user of the mobile device 102 via the SMS servers. It is to beappreciated that the ARED 106 may be configured to determine a user'sphone number and email address by cross referencing the deviceconfiguration information further illustrated in FIG. 5A, deviceactivity information further illustrated in FIG. 5B, and/or device userinformation further illustrated in FIG. 5C.

In embodiments where the mobile device 102 may be a designated leadmobile device 102 and the mobile device 102 may not be within physicalproximity of the ARED 106, the management component 214 may be generallyconfigured to perform active tracking operations. In these embodiments,the management component 214 may be configured to: (1) communicate withthe one or more follower mobile sensory devices 114-b and/or othermobile devices (not shown); and/or (2) receive device activityinformation generated by an activity component of a respective mobilesensory device and/or other mobile devices (e.g., activity component 216of mobile sensory device 114-1) within a tethered segment.

In embodiments where the mobile device 102 is configured to performactive tracking operations and after determining, by the proximitycomponent 220, that the one or more one or more mobile sensory devices114-b and/or other mobile devices within the tethered segment may leavethe physical proximity of the designated lead mobile device 102, themanagement component 214 may be further configured to activate at leastone feedback via the feedback component 218, which may include auditory,haptic, and/or visual feedback based on device configuration informationfurther discussed with respect to FIG. 5A.

In an embodiment, the activity component 216 may be generally configuredto assist in performing passive tracking operations. To assist inpassive tracking operations, the activity component 216 may be generallyconfigured to: (1) retrieve or otherwise receive motion information fromthe motion component 276 and orientation information from theorientation component 278; and (2) generate device activity informationfor the mobile device 102 based on the motion information andorientation information. Optionally, the activity component 216 may alsosupplement the device activity information with location informationreceived from the location component 288. The generated device activityinformation may be temporarily and cumulatively stored in the sensorydevice datastore 250 of memory 270 as time series data and retrieved bythe management component 214 for transmission to a designated leaddevice and/or ARED.

In an embodiment, the feedback component 218 may be generally configuredto provide visual feedback, auditory feedback, and/or haptic feedback,in response to an alert notification. In embodiments where the mobiledevice 102 is configured to perform passive tracking operations, themobile device 102 may be configured to receive the alert notificationwhich may be transmitted from the ARED 106 or another mobile device thatis performing active tracking operations. The receipt of the alertnotification may indicate that the ARED 106 or another mobile devicethat is performing the active tracking operations has determined and/orpredicted that a follower device may no longer be within physicalproximity of the designated lead device for a particular tetheredsegment of the mobile device 102. In embodiments where the mobile device102 is configured to perform active tracking operations, the proximitycomponent 220 may be configured to generate an alert notification, whenthe proximity component 220 determines and/or predicts that a followerdevice is no longer within physical proximity of the designated leaddevice within the tethered segment.

In an embodiment, the proximity component 220 may be generallyconfigured to assist a designated lead device (i.e., a designated leadmobile device) in performing active tracking operations. To performactive tracking operations, the proximity component 220 may be generallyarranged to: (1) determine whether a follower device (e.g., mobilesensory device 114-1, 114-2, etc.) is within physical proximity of adesignated lead device (e.g., mobile device 102); and/or (2) predictwhether the follower device will remain or leave the physical proximityof the designated lead device (e.g., mobile device 102) within atethered segment (e.g., tethered segment 118-1). Each of theseoperations will be further discussed below in turn and in the orderdiscussed above.

In an embodiment, the proximity component 220 may determine whether afollower device (e.g., mobile sensory device 114-1, 114-2, etc.) iswithin the physical proximity of a designated lead device (e.g., mobiledevice 102) by polling the one or more follower devices via directpeer-to-peer wireless connections and/or protocols (e.g., Bluetoothstandards, 802.11 wireless standards, etc.). In an embodiment, theproximity component 220 may determine that each of the follower devicewithin a tethered segment are within physical proximity of thedesignated lead device, when the proximity component 220 may communicatewith each of the follower device via one or more wireless connectionsand/or protocols on the local area network.

In an embodiment, and to poll the one or more follower devices, theproximity component 220 may be configured to determine whether each ofthe follower devices within a tethered segment is network reachable bythe designated lead device via a direct peer-to-peer wireless connectionto the one or more follower devices. Additionally or alternatively andto poll the one or more follower devices, the proximity component 220may be configured to request device activity information generated bythe activity component (e.g., activity component 316 of FIG. 3) of theone or more follower devices.

For example, the proximity component 220 may be configured to determinethat a follower device (e.g., mobile sensory electronic device 114-1)that is in the same tethered segment 118-1 as a designated lead device(e.g., mobile device 102), is also within the physical proximity of thedesignated lead device, when the proximity component 220 may ping orotherwise communicate with the follower device via a direct peer-to-peerwireless connection. Similarly, the proximity component 220 may beconfigured to determine that the one or more follower devices (e.g.,mobile sensory devices 114-1 and 114-2) may not be within physicalproximity of the designated lead device for a specific unit of time,when the proximity component 220 is unable to ping or otherwise unableto communicate with a follower device via a direct peer-to-peer wirelessconnection within a specific communication timeout period (e.g., 5seconds, 10 seconds, 30 seconds, 60 seconds, etc.).

In an embodiment and to perform active tracking operations, theproximity component 220 may be further configured to predict whether oneor more follower devices (e.g., mobile sensory device 114-1, 114-2,etc.) will remain within the physical proximity of a designated leaddevice (e.g., mobile device 102) within a tethered segment (e.g.,tethered segment 118-1, etc.). by: (1) receiving device activityinformation from the one or more follower devices that are moving; (2)updating the device activity information for each device stored in thedevice datastore 250 based on the received device activity datastore;and/or (3) polling the one or more follower devices, in response todetermining that designated lead device is moving based at leastpartially on the device activity information generated by the activitycomponent 216.

For example, the proximity component 220 may predict that a followerdevice such as mobile sensory electronic device 114-1 that is within thesame tethered segment 118-1 as a designated lead mobile device such asmobile device 102, will remain within physical proximity of the leaddevice, when the proximity component 220 determines that the mobiledevice 102 is moving substantially at the same time and/or substantiallyin the same direction as the mobile sensory device 114-1.

Continuing with the above example and to determine whether the mobiledevice 102 is moving substantially at the same time and/or substantiallyin the same direction as the mobile sensory device 114-1, the proximitycomponent 220 may be configured to compare the most recent in timedevice activity information of the mobile device 102, (i.e., the leaddevice activity information) with the most recent in time deviceactivity information of the at least one mobile sensory device such asmobile sensory devices 114-1 and 114-2 (i.e., the one or more followerdevice activity information).

Continuing with the above example, the proximity component 220 may befurther configured to analyze and compare the cumulative device activityinformation for a past time period (e.g., past five (5) seconds, pastten (10) seconds, etc.) immediately before the most recent in timedevice activity information for each of the at least one mobile sensorydevices or other mobile devices. For example and based on the analysisand comparison of the past cumulative and most recent in time deviceactivity information, the proximity component 220 may be configured todetermine that all devices within a tethered segment started moving atsubstantially same time, when the maximum time difference between afirst device to transition from a non-moving state to a moving state anda last device to transition from a non-moving state to a moving statedoes not exceed a specific period of time (e.g., 500 milliseconds, one(1) second, etc.).

Based on the above analyses and comparisons, the proximity component 220may be configured to determine that the mobile device 102 is movingsubstantially at the same time as the mobile sensory device 114-1 and114-2. As such, the proximity component 220 may predict that one or morefollower devices such as mobile sensory devices 114-1 and 114-2 mayremain within physical proximity of the lead device for a specific unitof time (e.g., 5 seconds, 10 seconds, 30 seconds, 60 seconds, etc.).

Continuing with the above example, the proximity component 220 may beconfigured to predict that the one or more follower devices such asmobile sensory devices 114-1 and 114-2 may not remain within physicalproximity of the lead device for a specific unit of time, when theproximity component 220 determines that the mobile device 102 is notmoving substantially at the same time or not moving substantially in thesame direction as the mobile sensory device 114-1 and 114-2.

Based on the above prediction, determination, and the deviceconfiguration information, the proximity component 220 may also beconfigured to generate an alert notification, which may be used by thefeedback component 218 to provide auditory, haptic, and/or visualfeedback to notify the user of the mobile device 102 that one or morefollower devices such as the mobile sensory device 114-1 and/or 114-2within the tethered segment 118-1 will not be within physical proximityof the mobile device 102. Additionally and based on the deviceconfiguration information, the alert notification may be transmitted tothe one or more mobile sensory device 114-1 and/or 114-2 that did notmove in substantially the same direction and/or at substantially thesame time as mobile device 102.

FIG. 3 illustrates a block diagram of an example embodiment of themobile sensory device 114-1. It is to be appreciated that while FIG. 3illustrates one example embodiment of the mobile sensory device 114-1,the example embodiment is not limited to this context. Additionally, itis to be appreciated those other mobile sensory devices (e.g., mobilesensory device 114-2, 114-3 . . . 114-b) may be similarly configured.

In an embodiment, the mobile sensory device 114-1 may be generallyarranged to provide physical proximity tracking of a coupled utilitydevice and may include, without limitation, memory 370, communicationscomponent 374, motion component 376, and orientation component 378,acoustic output component 380, haptic component 382, embedded processorcomponent 384, visual indicator component 386, internal power component390, where each of the components and memory 370 may be operativelyconnected via interconnect 392.

In an embodiment, the memory 370 may be generally arranged to storeinformation in volatile and/or nonvolatile memory, which may include,but is not limited to, the memory previously discussed with respect tomemory 270 and/or any other type of storage media configured for storinginformation. In an embodiment and similar to memory 270, the memory 370may include instruction information arranged for execution by theembedded processor component 384. In that embodiment, the instructioninformation may be representative of at least one embedded operatingsystem 372, one or more applications, which may include, but is notlimited to, sensory device control application 312. In an embodiment,the memory 370 may further include sensory device datastore 350 whichmay be configured to store at least a portion of device configurationinformation further illustrated in FIG. 5A, device activity informationfurther illustrated in FIG. 5B, and device user information furtherillustrated in FIG. 5C.

In an embodiment, the embedded operating system 372 may include, withoutlimitation, light weight real-time and/or embedded operating systems(e.g., Texas Instruments Inc.® TI-RTOS, Wind River Systems® VxWorks®,etc.) general arranged to manage a limited set of hardware resources(e.g., one or more components of the mobile sensory device 114-1, etc.)and/or software resources (e.g., one or more applications of the mobilesensory device 114-1, etc.).

In an embodiment, the communications component 374 may be generallyarranged to enable the mobile sensory device 114-1 to communicate,directly and/or indirectly, with various devices (e.g., mobile device102, ARED 106, etc.) in the mobile sensory system 100. Thecommunications component 374 may include, among other elements, a radiofrequency circuit (not shown) configured for encoding and/or decodinginformation and receiving and/or transmitting the encoded information asradio signals in frequencies consistent with the one or more wirelesscommunications standards (e.g., Bluetooth, Wireless IEEE 802.11, WiMAXIEEE 802.16, Global Systems for Mobile Communications (GSM), EnhancedData Rates for GSM Evolution (EDGE), Long Term Evolution (LTE),Bluetooth standards, Near Field Communications (NFC) standards, etc.).

In an embodiment, the motion component 376 may be generally arranged todetect motion of the mobile sensory device 114-1 in one or more axes.The motion component 376 may include, among other elements, motionsensor (e.g., accelerometer, micro gyroscope, etc.) to convert physicalmotions applied to or exerted on the mobile sensory device 114-1 intomotion information.

In an embodiment, the orientation component 378 may be generallyarranged to detect magnetic fields for measuring the strength ofmagnetic fields surrounding the mobile device 102. The orientationcomponent 378 may include, among other elements, magnetic sensor (e.g.,magnetometer, magnetoresistive permalloy sensor, etc.) to convertmagnetic field applied to or exerted on the mobile sensory device 114-1into orientation information, which may identify a number of degreesfrom a reference orientation the mobile device 102 is oriented orotherwise pointed.

In an embodiment, the acoustic output component 380 may be generallyarranged to receive acoustic output information and convert the receivedacoustic output information into electronic signals to output sound,vibrations, or any other mechanical waves. To convert the receivedacoustic output information to mechanical waves, acoustic outputcomponent 380 may utilize the one or more electroacoustic transducers(e.g., speakers, etc.), which may be located or positioned on or withinthe housing, case, or enclosure of the mobile sensory device 114-1.

In an embodiment, the haptic component 382 may be generally arranged toprovide tactile feedback with varying strength and/or frequency withrespect to time through the housing, case, or enclosure of the mobilesensory device 114-1. Moreover, the haptic component 382 may include,among other elements, a vibration circuit (e.g., an oscillating motor,vibrating motor, etc.) arranged to receive haptic output information andconvert the received haptic output information to mechanical vibrationsrepresentative of tactile feedback.

In an embodiment, the embedded processor component 384 may be generallyarranged to execute instruction information including one or moreinstructions. In an embodiment, the embedded processor component 384 maybe an embedded processor component or system-on-chip (SoC) processorcomponent which may comprise, among other elements, a processor circuit,which may include, but is not limited to, at least one set of electroniccircuits arranged to execute one or more instructions. Additionally oralternatively, the embedded processor component 384 may be an embeddedmicrocontroller component arranged to execute the one or moreinstructions.

In an embodiment, the visual indicator component 386 may be generallyarranged to receive and present visual display information. Moreover,the visual indicator component 386 may include, among other elements,micro-display device (e.g., liquid-crystal display, light-emitting diodedisplay, organic light-emitting diode display, etc.) for presenting thevisual display information. Additionally or alternatively, the visualindicator component 386 may include one or more light-emitting diodesand/or organic light-emitting diodes mounted on the surface of themobile sensory device to provide visual feedback.

In an embodiment, the internal power component 390 may be generallyarranged to provide power to the various components and the memory ofthe mobile sensory device 114-1. In an embodiment, the internal powercomponent 390 may include and/or be operatively coupled to an internaland/or external battery configured to provide power to the variouscomponents (e.g., communications component 374, motion component 376,memory 370, etc.). Additionally or alternatively, the internal powercomponent 390 may generate and/or store power from surroundingelectromagnetic radiation to power the one or more components of themobile device 114-1 or otherwise charge the internal and/or externalbattery (not shown).

In an embodiment, the sensory device control application 312 may begenerally configured to the mobile device control application 212 mayalso be generally configured to perform passive tracking operations thatpassively assist in tracking of the mobile sensory device 114-1 in alimited geographical area surrounding a designated lead mobile device oran ARED. In an embodiment, the sensory device control application 312may include, without limitation, management component 314, activitycomponent 316, and feedback component 318.

In an embodiment and to perform the passive tracking operations, themanagement component 314 may be configured to detect movement of themobile sensory device 114-1. In response to the detection of movement ofthe mobile sensory device 114-1, the management component 314 may beconfigured to: (1) transition the mobile sensory device 114-1 from alower energy consumption state to a higher energy consumption state; (2)connect with a mobile device (e.g., mobile device 102) or an ARED (e.g.,ARED 106); and (3) transmit device activity information to a designatedlead device (e.g., mobile device 102 which may be a designated leadmobile device) or an ARED, in response to detecting movement of themobile sensory device 114-1.

In an embodiment, the management component 314 may also be configured to(1) connect to a mobile device (e.g., mobile device 102 which may be adesignated lead mobile device) or an ARED (ARED 106); and (2) receive adevice activity request from a mobile device (e.g., mobile device 102which may be a designated lead mobile device) or an ARED (ARED 106). Inresponse to receiving the device activity request, the managementcomponent 314 may be configured to: (1) optionally transition the mobilesensory electronic device from a lower-energy consumption state to ahigh-energy consumption state; (2) retrieve the requested deviceactivity information from the device datastore 350; (3) transmit deviceactivity information to the mobile device or the ARED that transmittedthe device activity request; and/or (4) optionally transition the mobilesensory electronic device from a higher-energy consumption state to alower-energy consumption state.

In an embodiment, the management component 314 may be further configuredto receive an alert notification from a mobile device or ARED that isperforming active tracking operations. The receipt of the alertnotification may indicate that the mobile device or ARED that isperforming the active tracking operations has determined and/orpredicted that a follower device (e.g., mobile sensory device 114-1) mayno longer be within physical proximity of the designated lead device(e.g. mobile device 102) for a particular tethered segment (e.g.,tethered segment 118-1). In response to receiving the alertnotification, the management component 314 may be configured to: (1)optionally transition the mobile sensory device 114-1 from a lowerenergy consumption state to a higher energy consumption state; (2)provide the alert notification to the feedback component 318 to providefeedback (e.g., visual feedback, an auditory feedback, haptic feedback)via the acoustic output component 380, haptic component 382, and/orvisual indicator component 386; and/or (3) transition the mobile sensorydevice 114-1 from the previously higher-energy consumption state to thelower-energy consumption state.

In an embodiment and based on cumulative device activity information,the management component 314 may also be configured to detectnon-movement of the mobile sensory device 114 for a specific unit oftime (e.g., 5 seconds, 10 seconds, 30 seconds, etc.), i.e., the mobilesensory device 114-1 remains stationary for the specific unit of time.In response to the detection of non-movement, the mobile sensory device114-1 may be configured to: (1) disconnect from any connected mobiledevice or ARED; and/or (2) optionally transition the mobile sensorydevice 114-1 from a higher energy consumption state to a lower energyconsumption state, when the mobile sensory device 114-1 was previouslyin a higher-energy consumption state in order to reduce powerconsumption from the internal power component 390.

In an embodiment, the activity component 316 may be generally to assistin performing passive tracking operations. To assist in passive trackingoperations, the activity component 316 may be configured to: (1)retrieve or otherwise receive motion information from the motioncomponent 276 and orientation information from the orientation component278; and (2) generate device activity information for the mobile sensorydevice 114-1 based on the motion information and orientationinformation. The generated device activity information may betemporarily and cumulatively stored in the sensory device datastore 350of memory 370 as time series data and retrieved by the managementcomponent 314 for transmission to a mobile device and/or ARED.

In an embodiment, the feedback component 318 may be generally configuredto provide visual feedback, auditory feedback, and/or haptic feedback,in response to an alert notification. In an embodiment, the mobilesensory device 114-1 may be configured to receive the alert notificationtransmitted from a mobile device or ARED, when the mobile device or AREDdetermines and/or predicts that a follower device (e.g., mobile sensorydevice 114-1) is no longer within physical proximity of the designatedlead device (e.g., mobile device 102) for a particular tethered segment(e.g., tethered segment 118-1).

FIG. 4 illustrates a block diagram of an example embodiment of the ARED106. It is to be appreciated that while FIG. 4 illustrates one exampleembodiment of the ARED 106, the example embodiment is not limited tothis context.

In an embodiment, the ARED 106 may be generally configured to receiveacoustic input in the form of audio commands (e.g., verbal, spoken,etc.) from a user or another source of audio commands (such as but notlimited to the audio of content output by speakers of display device(not shown)). In response, the ARED 106 may be configured to transmitcontrol signals corresponding to such audio commands to various devicesthat may be connected to the network 150 such as one or more mediadevice(s) (e.g., Roku® Streaming Stick®, Amazon® Fire TV®, Google®,Chrome Cast®, etc.)(not shown), display device(s) (e.g., Samsung® SmartTV® display devices, LG® WebOS® display devices, etc.)(not shown),digital assistant(s) (e.g., Amazon® Echo®/Alexa®, Apple® iPhone®/Siri®,Microsoft®/Cortana®, Google Home®/Google Assistant®)(not shown) and/orany other device in mobile sensory system 100, to cause the one or moremedia device(s), display device(s), digital assistant(s) and/or othercomponent to operate according to the audio commands.

In an embodiment, the ARED 106 may also be configured to assist in thephysical proximity tracking of one or more mobile devices (e.g., mobiledevice 102, etc.) and/or mobile sensory devices (e.g., mobile sensorydevice 114-1, 114-2, 114-3, etc.) in a local area or fixed area such asa business office and/or home residence. In an embodiment, the devicemay include, but is not limited to, memory 470, communications component474, beam forming component 480, acoustic output component 482,processor component 484, visual indicator component 486, power component490, where each of the components and memory 270 may be operativelyconnected via interconnect 492.

In an embodiment, the memory 470 may be generally arranged to storeinformation in volatile and/or nonvolatile memory, which may include,but is not limited to, the memory previously discussed with respect tomemory 270, memory 370, and/or any other type of storage mediaconfigured for storing information. In an embodiment and similar tomemory 270 and memory 370, the memory 470 may include instructioninformation arranged for execution by the processor component 484. Inthat embodiment, the instruction information may be representative of atleast one operating system 472, one or more applications, which mayinclude, but is not limited to, ARED control application 412. In anembodiment, the memory 470 may further include device datastore 450which may be configured to store device configuration informationfurther illustrated in FIG. 5A, device activity information furtherillustrated in FIG. 5B, and device user information further illustratedin FIG. 5C.

In an embodiment, the operating system 472 may be generally arranged tomanage a limited set of hardware resources (e.g., one or more componentsof the mobile sensory device 114-1, etc.) and/or software resources(e.g., one or more applications of the mobile sensory device 114-1,etc.). In an embodiment, the operating system 472 may include, withoutlimitation, light weight real-time embedded operating systems such asthose discussed with respect to mobile sensory device 114-1.Alternatively, the operating system 472 may include, without limitation,mobile operating systems such as those discussed with respect to mobileoperating system 272 of mobile device 102.

In an embodiment, the communications component 474 may be generallyarranged to enable the ARED 106 to communicate, directly and/orindirectly, with various devices (e.g., mobile device 102, mobilesensory device 114-1, 114-2, Mail Transfer Agents (MTA) (not shown),Short Messaging Service (SMS) servers (not shown), etc.) in the mobilesensory system 100. In an embodiment, the communications component 474may include, among other elements, a radio frequency circuit (not shown)configured for encoding and/or decoding information and receiving and/ortransmitting the encoded information as radio signals in frequenciesconsistent with the one or more wireless communications standards (e.g.,Bluetooth, Wireless IEEE 802.11, WiMAX IEEE 802.16, Global Systems forMobile Communications (GSM), Enhanced Data Rates for GSM Evolution(EDGE), Long Term Evolution (LTE), Bluetooth standards, Near FieldCommunications (NFC) standards, etc.).

In an embodiment, the beam forming component 480 may be generallyarranged for converting sound, vibrations, or any other mechanical wavesreceived by the ARED 106 into digital or electronic signalsrepresentative of acoustic input information. To convert thesemechanical waves into acoustic input information, the beam formingcomponent 480 may be configured to utilize one or more acoustic sensors(e.g., microphones, etc.), which may be located or positioned on orwithin the housing, case, or enclosure of the ARED 106 to form anmicrophone array.

In an embodiment, the acoustic output component 482 may be generallyarranged to receive acoustic output information and convert the receivedacoustic output information into electronic signals to output sound,vibrations, or any other mechanical waves. To convert the receivedacoustic output information to mechanical waves, acoustic outputcomponent 482 may utilize the one or more electroacoustic transducers(e.g., speakers, etc.) which may be located or positioned on or withinthe housing, case, or enclosure of the ARED 106.

In an embodiment, the processor component 484 may be generally arrangedto execute instruction information including one or more instructions.In an embodiment, the processor component 484 may be an embeddedprocessor component or system-on-chip (SoC) processor component whichmay comprise, among other elements, processor circuit, which mayinclude, but is not limited to, at least one set of electronic circuitsarranged to execute one or more instructions. Additionally oralternatively, the processor component 484 may be an embeddedmicrocontroller component or mobile processor component arranged toexecute the one or more instructions.

In an embodiment, the visual indicator component 486 may be generallyarranged to receive and present visual display information. Moreover,the visual indicator component 386 may include, among other elements,micro-display device (e.g., liquid-crystal display, light-emitting diodedisplay, organic light-emitting diode display, etc.) and/or one or morelight-emitting diodes and/or organic light-emitting diodes mounted onthe surface of the ARED 106 to provide visual feedback.

In an embodiment, the power component 490 may be generally arranged toprovide power to the various components and the memory of the ARED 106.In an embodiment, the internal power component 490 may include and/or beoperatively coupled to an internal and/or external battery configured toprovide power to the various components (e.g., processor component 484,communications component 474, memory 470, etc.). Additionally oralternatively, the power component 490 may receive and/or store powerprovided by a power source 108 such as, for example, a power outlet.

In an embodiment, the user interface application 430 may be generallyconfigured to process audio commands received from a user or anothersource of audio commands (such as but not limited to the audio ofcontent output by speakers of display device (not shown)). In response,the ARED 106 may be configured to convert the processed audio commandsand generate control signals based on the processed audio commands thatare specifically adapted for the control of one or more media device(s),display device(s), digital assistant(s), and/or any other device thatmay be in mobile sensory system 100. Additionally, the ARED 106 maytransmit control signals corresponding to such audio commands to variousdevices that may be connected to the network 150.

In an embodiment, the ARED control application 412 may be generallyconfigured to perform active tracking operations that actively assist intracking of various utility objects 112-b and/or mobile devices within alimited geographical area surrounding the ARED 106. The limitedgeographical area may include a local area network 150, which mayinclude, without limitation, geographical area surrounding a businessoffice, home residence, or any other limited geographical area that istypically reachable by the local area network 150. In an embodiment, theARED control application 412 may include, without limitation, amanagement component 414, a feedback component 418, and a proximitycomponent 420.

In an embodiment and to perform active tracking operations, themanagement component 414 may be generally configured to: (1) communicatewith the one or more mobile sensory devices 114-b and/or mobile devices;and (2) request and/or receive device activity information generated byan activity component of a respective mobile sensory device (e.g.,activity component 316 of mobile sensory device 114-1) and/or mobiledevices (e.g., activity component 216 of mobile devices) within atethered segment.

In an embodiment, the feedback component 418 may be generally configuredto provide visual feedback, auditory feedback, and/or haptic feedback,in response to an alert notification. In an embodiment, the proximitycomponent 220 may generate the alert notification, when the proximitycomponent 420 determines and/or predicts that a follower device is nolonger within physical proximity of the designated lead device withinthe tethered segment.

In an embodiment, the proximity component 420 may be generallyconfigured to assist the ARED 106 in performing active trackingoperations. To perform active tracking operations, the proximitycomponent 420, for each tethered segment (e.g., tethered segment 118-1,118-2, etc.), may be generally arranged to: (1) determine that at leastone device (e.g., mobile sensory device 114-1, 114-2, etc.) for atethered segment is not within a limited geographical area surroundingthe ARED 106; and (2) determine that at least one other device (e.g.,mobile device 102) in the same tethered segment is within the limitedgeographical area surrounding the ARED 106. Additionally, the proximitycomponent 420, for each tethered segment (tethered segment 118-1, 118-2,etc.), may be also generally arranged to predict whether all devicescurrently within limited geographical area surrounding the ARED 106 willalso remain or leave the physical proximity of each other. Each of theseoperations will be further discussed below in turn and in the orderdiscussed above.

In an embodiment, the proximity component 420 may be configured todetermine whether a follower device (e.g., mobile sensory device 114-1,114-2, etc.) and a designated lead device (e.g., mobile device 102) iswithin the physical proximity of each other in a limited geographicalarea surrounding the ARED 106. To perform the above determinations, theproximity component 420 may be configured to poll the one or morefollower devices and/or the designated lead device via wirelessconnections and/or protocols on a local area network (e.g., Bluetoothstandards, 802.11 wireless standards, etc.). In an embodiment, and topoll the one or more follower devices, the proximity component 420 maybe further configured to determine whether each of the follower devicesand the designated lead device within a tethered segment is networkreachable via either direct peer-to-peer wireless connections to the oneor more devices or network reachable via local area network connectionof the ARED 106. Additionally or alternatively and to poll the one ormore devices, the proximity component 420 may be configured to requestdevice activity information generated by the activity component (e.g.,activity component 216 of FIG. 2 and activity component 316 of FIG. 3)from the one or more devices.

In an embodiment and for each tethered segment (e.g., tethered segment118-1, 118-2, etc.), the proximity component 420 may be configured todetermine that at least one follower device (e.g., mobile sensory device114-1, 114-2, etc.) and/or a designated lead device (e.g., mobile device102) is not within a limited geographical area surrounding the ARED 106.Additionally, the proximity component 420 may also be configured todetermine that at least one other follower device (e.g., mobile sensorydevice 114-1, 114-2, etc.) and/or the designated lead device (e.g.,mobile device 102) are within the limited geographical area surroundingthe ARED 106.

Thus, in the embodiment above, the proximity component 420 may determinethat a first device is not within the limited geographical areasurrounding ARED 106 and also determine that a second device is withinlimited geographical area surrounding ARED 106. This allows theproximity component 420 to determine that the first device for atethered segment is outside of the approximate physical proximity of thesecond device in the same tethered segment, which may indicate that theuser has forgotten a utility object.

For example, the proximity component 420 may be configured to determinethat a mobile sensory device 114-1 of tethered segment 118-1 is withinthe physical proximity of ARED 106, when the proximity component 420 mayping or otherwise communicate with both the follower device and thedesignated lead device via a direct peer-to-peer wireless connection orthe local area network connection of the ARED 106. Similarly, theproximity component 420 may be configured to determine that the mobilesensory device 114-2 may not be within physical proximity of the ARED106 for a specific unit of time, when the proximity component 420 isunable to ping or otherwise unable to communicate with the mobilesensory device 114-2 via a direct peer-to-peer wireless connection orthe local area network connection of the ARED 106 for a specificcommunication timeout period (e.g., 5 seconds, 10 seconds, 30 seconds,60 seconds, etc.). This may indicate that the mobile sensory device114-2 attached to utility object 112-2 may have traveled outside theapproximate physical proximity of the mobile sensory device 114-1.

Additionally, the proximity component 420 may determine that all devicesof a tethered segment are within physical proximity of the ARED 106 andtherefore all devices are also within approximate physical proximity ofeach other, when the ARED 106 may communicate with each device withinthe tethered segment via one or more wireless connections and/orprotocols on the local area network. Upon the above determination thatall devices of a tethered segment are within substantial physicalproximity of each other, the proximity component 420 may be furtherconfigured to predict whether one or more devices (e.g., mobile sensorydevices 114-1, 114-2, etc.) will remain within or leave the physicalproximity of a designated lead device (e.g., mobile device 102) within atethered segment (e.g., tethered segment 118-1, etc.)

In an embodiment and to predict whether one or more follower devices(e.g., mobile sensory devices 114-1, 114-2, etc.) will remain within orleave the physical proximity of a designated lead device (e.g., mobiledevice 102) within a tethered segment (e.g., tethered segment 118-1,etc.), the proximity component 420 may be configured to: (1) receivedevice activity information from the one or more devices that aremoving; (2) update the device activity information for each devicestored in the device datastore 250 based on the received device activitydatastore; and/or (3) poll the one or more devices, in response todetermining that at least one device is moving based at least partiallyon the received device activity information.

In an embodiment and to predict whether one or more follower devices(e.g., mobile sensory devices 114-1, 114-2, etc.) will remain within orleave the physical proximity of a designated lead device (e.g., mobiledevice 102), the proximity component 420 may be configured to determinewhether all devices within the tethered segment are moving atsubstantially the same time and/or substantially in the same direction.For example, the proximity component 420 may predict that a followerdevice such as mobile sensory electronic device 114-1 that is within thesame tethered segment 118-1 as a designated lead device such as mobiledevice 102, will remain within physical proximity of the lead device,when the proximity component 420 determines that the mobile device 102is moving substantially at the same time and/or in substantially thesame direction as the mobile sensory device 114-1.

Continuing with the above example and to determine whether the mobiledevice 102 is moving substantially at the same time and/or substantiallyin the same direction as the mobile sensory device 114-1, the proximitycomponent 420 may be configured to compare the past cumulative deviceactivity information and most recent in time device activity informationof the mobile device 102, (i.e., the lead device activity information)with the past cumulative device activity information and most recent intime device activity information of the at least one mobile sensorydevice such as mobile sensory devices 114-1 and 114-2 (i.e., the one ormore follower device activity information). Continuing with the aboveexample, and based on the analysis and comparison of the past cumulativeand most recent in time device activity information, the proximitycomponent 420 may be configured to determine that all devices within atethered segment started moving at substantially same time, when themaximum time difference between a first device to transition from anon-moving state to a moving state and a last device to transition froma non-moving state to a moving state does not exceed a specific periodof time (e.g., 500 milliseconds, one (1) second, etc.).

Based on the above prediction, determination, and the deviceconfiguration information, the proximity component 420 may also beconfigured to generate an alert notification. In an embodiment, thealert notification may be used by the feedback component 418 to provideauditory, haptic, and/or visual feedback. The feedback may notify theuser of the mobile device 102 that one or more follower devices (e.g.,mobile sensory device 114-1, 114-2, etc.) of a tethered segment (e.g.,tethered segment 118-1) is not within approximate physical proximity ofeach other or predicted to not remain within the approximate physicalproximity of each other. Additionally and based on the deviceconfiguration information, the alert notification may be transmitted tothe at least one follower device (e.g., mobile sensory device 114-1and/or 114-2) that did not move in substantially the same directionand/or at substantially the same time as mobile device 102.

FIG. 5A illustrates example device configuration information for mobiledevices and/or mobile sensory devices that may be stored within thedevice datastore 250, device datastore 350, and device datastore 450according to an example embodiment.

In an embodiment, the device configuration information for each mobiledevice and/or mobile sensory device may include, without limitation,user identifier that identifies a particular user (e.g., a uniqueidentifier of alphanumeric characters, etc.) associated with the device,a device identifier that uniquely identifies the particular device(e.g., media access control (MAC) address, Electronic Serial Number(ESN), etc.)), a device type that identifies the device as a mobiledevice or a mobile sensory device, a segment identifier that identifiesthe tethered segment that the device is associated with (e.g., a uniqueidentifier of alphanumeric characters, etc.), a leader/followerindicator that indicates whether the device is a designated lead deviceor a follower device within a tethered segment, and/or feedbackindicator that identifies the types of feedback that is enabled for thatparticular device (e.g., audio feedback, haptic feedback, visualfeedback, email feedback, message feedback, etc.).

For example and with respect to the device identifier, Device_ID_1 maybe associated with and identify mobile device 102, Device_ID_2 may beassociated with and identify mobile sensory device 114-1, Device_ID_3may be associated with and identify mobile sensory device 114-2 and soforth. Continuing with the example and with respect to the segmentidentifier, Segment_ID_1 may be associated with and identify tethersegment 118-1 which may include Device_ID_1, Device_ID_2, andDevice_ID_3, which may all be associated with the user name John Doehaving user identifier of USER_ID_1 as illustrated in combination withFIG. 5C.

FIG. 5B illustrates example device activity information for one or moremobile devices and/or mobile sensory devices that may be stored withinthe device datastore 250, device datastore 350, and device datastore 450according to an example embodiment.

In an embodiment, the device activity information for each mobile deviceand/or mobile sensory device may include, without limitation, a deviceidentifier that uniquely identifies the particular device, locationinformation that identifies the approximate longitude and latitudecoordinates associated with the device (when available), motion statethat identifies whether the device is in a moving state or not moving ornon-moving state, motion direction that identifies the approximatedirection of the motion (e.g., North (N), South (S), East (E), West,(W), and combinations thereof such as North West (NW), North East (NE),South West (SW), South East (SE), etc.) and/or update timestamp thatindicates the time that the device activity information was last updatedby the mobile device 102 and/or ARED 106 for the device (e.g., mobiledevice 102, mobile sensory device 114-1, 114-2, etc.). Furthermore, inan embodiment, the device activity information stored in the variousdevice datastores may be cumulated and/or aggregated as time series datawhere each update to the device activity information may include acorresponding update time stamp (e.g., UNIX time stamp in millisecondresolution as illustrated in FIG. 5B) and updated values for each of theone or more entries (i.e., time series device activity information).

FIG. 5C illustrates device user information for one or more mobiledevices and/or ARED 106 that may be stored within the device datastore250 and device datastore 450 according to an example embodiment.

In an embodiment, the device user information for each mobile deviceand/or mobile sensory device may include, without limitation, a useridentifier that identifies a particular user (e.g., a unique identifierof alphanumeric characters, etc.) associated with the device, the username associated with the user identifier, a phone number associated withthe user identifier, and/or email address associated with the useridentifier.

It is to be appreciated that by using device user information (e.g.,user identifier, user name, phone number, email address, etc.) as wellas segment identifier and device identifier, the various information(e.g., motions state, motion direction, device type, leader/follower,feedback, etc.) associated with device configuration information and/ordevice activity information for each device (e.g., mobile device, mobilesensory device, etc.), the one or more components (e.g., managementcomponents) of the mobile device, mobile sensory device, and/or ARED mayefficiency determine various information by cross referencing withvarious identifiers (e.g., the segment identifier, device identifier,and user identifier).

Provided herein below are example processing operations that may beperformed by one or more example embodiments. Although the processingoperations may appear to be performed sequentially, it is to beappreciated that the processing operations may not be limited to theorder as illustrated and/or described. Additionally, some processingoperations may occur substantially simultaneously or contemporaneouslywith respect to other processing operations as will be further discussedbelow.

FIGS. 6A and 6B illustrate example processing operations an ARED mayperform to actively track the approximate physical proximity ofdifferent devices of a tethered segment. In various embodiments of FIGS.6A and 6B, the ARED may perform active tracking operations to determineand/or predict whether one or more devices within a tethered segment arewithin physical proximity of a designated lead device or will remainwithin or leave the physical proximity of the designated lead deviceaccording to example embodiments.

In the various embodiments of FIGS. 6A and 6B, the mobile device 102,the mobile sensory device 114-1, and the mobile sensory device 114-2 maybe within the same tethered segment 118-1 and each of the devices may bewithin the predefined area 650 of the ARED 106 to facilitate wirelesscommunications with the ARED 106 either directly or indirectly over alocal area network associated with the ARED 106. In various embodimentsof FIGS. 6A and 6B, the predefined area 650 may be representative of alimited or fixed geographical region such as a business office and/orhome residence where each of the devices in the tethered segment 118-1may communicate either directly or indirectly over a local area networkassociated with the ARED 106. Additionally and in various embodiments ofFIGS. 6A and 6B, the mobile device 102 may be designated as a leaddevice and the mobile sensory devices 114-1 and 114-2 may be designatedas follower devices. In various embodiments of FIGS. 6A and 6B, themobile device 102 and the mobile sensory device 114-1 may begin to moveas illustrated at stages 652-1 and 652-2 while the mobile sensory 114-2may remain stationary.

In an embodiment and to determine whether devices in the tetheredsegment 118-1 are within the predefined area 650 of the ARED 106, theARED 106 may be configured to poll the one or more follower devicesand/or the designated lead device via wireless connections and/orprotocols in the local area network of the ARED 106. In an embodiment,the ARED 106 may determine whether the mobile sensory devices 114-1 and114-2 and the mobile device 102 are within predefined area 650 of theARED 106, when the ARED 106 may communicate with each device in thetethered segment 118-1 via one or more wireless connections and/orprotocols on the local area network.

In an embodiment, the ARED 106 may determine that the one or moredevices such as the mobile device 102, mobile sensory device 114-1and/or mobile sensory device 114-2 may not be within physical proximityof ARED 106, when the ARED 106 is unable to ping or otherwise unable tocommunicate with the one or more devices within a specific communicationtimeout period (e.g., five hundred (500) milliseconds, one (1) second,two (2) seconds, ten (10) seconds, etc.) In response to thatdetermination, the ARED 106 may transmit one or more alert notificationsto the one or more devices within the tethered segment 118-1 to indicatethat the one or more devices are not within the tethered segment 118-1.

Alternatively and as illustrated in FIG. 6A at stages 610-1, 610-2, and610-3, the ARED 106 may determine that the ARED 106 may communicate withthe one or more devices such as the mobile device 102, mobile sensorydevice 114-1, and mobile sensory device 114-2 within the tetheredsegment 118-1. Assuming that the ARED 106 may communicate with each ofthe devices in tethered segment 118-1, at stages 610-1, 610-2, and610-3, the ARED 106 may also optionally request and receive deviceconfiguration information from each device within the tethered segment118-1. In response to receiving the device configuration information forone or more devices, the ARED 106 may also optionally update the deviceconfiguration information of the one or more devices stored in thedevice datastore 450. While not explicitly illustrated, it is to beappreciated that the one or more stages (e.g., stages 610-1, 610-2, and610-3) may be performed substantially simultaneously orcontemporaneously between the ARED 106 and various devices within thetethered segment 118-1. Additionally or alternatively, the one or morestages (e.g., stages 610-1, 610-2, and 610-3) may also be performed inany order.

In an embodiment and to predict whether each of the devices within thetethered segment 118-1 will remain within the tethered segment 118-1when the one or more devices in the tethered segment 118-1 moves, theARED 106 may determine whether the devices in the tethered segment 118-1are moving substantially at the same time and/or substantially in thesame direction. In an embodiment and at stages 612-1 and 612-2, both themobile device 102 and the mobile sensory device 114-1 may transmit theirrespective device activity information to the ARED 106, when the mobiledevice 102 and the mobile sensory device 114-1 begin to move asindicated by stages 652-1 and 652-2. When mobile device 102 and themobile sensory device 114-1 begin to move, both devices may transitionfrom a non-motion state (i.e., not moving state as illustrated in FIG.5B) to a motion state (e.g., moving state as illustrated in FIG. 5B)after detecting motion and/or acceleration by their respective activitycomponents (e.g., activity components 216 and 316 as illustrated inFIGS. 2 and 3).

In an embodiment and at stages 612-1 and 612-2, the ARED 106 may alsoreceive the device activity information transmitted from mobile device102 and mobile sensory device 114-1. In response, the ARED 106 may alsoupdate the device configuration information of the mobile device 102 andmobile sensory device 114-1 stored in the device datastore 450. In anembodiment, the ARED 106 may wait for a specific update timeout period(e.g., two hundred fifty milliseconds (250), five hundred (500)milliseconds, one (1) second, etc.) after receiving device configurationinformation from the mobile device 102 or mobile sensory device 114-1 inorder to provide sufficient time for the ARED 106 to receive deviceactivity information generated and/or transmitted from the mobilesensory device 114-2.

Additionally at stage 612-3 and after waiting for the specific updatetimeout period, the ARED 106 may optionally request the deviceconfiguration information from mobile sensory device 114-2. Additionallyat stage 612-3, the ARED 106 may optionally further wait for anotherspecific communication timeout period to receive the deviceconfiguration information to be generated and/or transmitted from themobile sensory device 114-2.

In an embodiment, and after waiting for one or more timeout periodsdiscussed above, the ARED 106 may begin to determine whether all deviceswithin the tethered segment 118-1 are moving substantially at the sametime and substantially in the same direction for a minimum continuousmovement period. In an embodiment and to determine whether the mobiledevice 102, mobile sensory device 114-1, and mobile sensory device 114-2are moving together substantially at the same time and/or substantiallyin the same direction, the ARED 106 may compare the past cumulativedevice activity information starting with the most recent in time ofmobile device 102, mobile sensory device 114-1, and mobile sensorydevice 114-2.

For example, the ARED 106 may compare past cumulative and most recent intime device activity information (e.g., past five (5) seconds from themost recent in time device activity information) received from themobile device 102, (i.e., the lead device activity information) with thepast cumulative and most recent device activity information (e.g., pastfive (5) seconds from the most recent in time device activityinformation) received from the one or more mobile sensory devices suchas mobile sensory devices 114-1 and 114-2 (i.e., the one or morefollower device activity information). Continuing with the example andin particular, the ARED 106 may compare at least the locationinformation, motion state, and/or motion direction of the mobile device102 with respect to the mobile sensory devices 114-1 and 114-2 todetermine whether the mobile device 102, mobile sensory device 114-1,and mobile sensory device 114-2 are moving together.

In an embodiment and based on the comparison of the device activityinformation of mobile device 102 and mobile sensory device 114-1, theARED 106 may determine that the mobile device 102 are in a substantiallysimilar location, moving substantially at the same time, and movingsubstantially in the same direction as the mobile sensory device 114-1.As such, the ARED 106 may predict that mobile device 102 and mobilesensory devices 114-1 may remain within physical proximity of each otherfor a specific period of time (e.g., five (5) seconds, ten (10) seconds,thirty (30) seconds, sixty (60) seconds, etc.). However, based on thecomparison of device activity information of the mobile device 102 andmobile sensory device 114-2, the ARED 106 may predict that mobile device102 and mobile sensory device 114-2 may not remain within physicalproximity of each other because they are not moving substantially at thesame time or moving substantially in the same direction with respect toeach other.

In an embodiment and after predicting that one or more devices (e.g.,mobile sensory device 114-2) within the tethered segment 118-1 may notremain within physical proximity of each other, then at stages614-1,614-2, and 614-3, the ARED 106 may transmit one or more alertnotifications to the one or more devices in the tethered segment 118-1.In some embodiments, the ARED 106 may transmit one or more alertnotifications to the only the moving devices or the only non-moving(e.g., stationary) devices. For example, the ARED 106 may transmit thealert notifications to only mobile device 102 and mobile sensory device114-1 or only the non-moving devices such as only mobile sensory device114-2.

Additionally or alternatively, the ARED 106 itself may provide at leastone feedback to the user. The at least one feedback provided by ARED 106may notify the user near the physical proximity of the ARED 106 that themobile sensory device 114-2 of tethered segment 118-1 which is currentlywithin the physical proximity of ARED 106 may not remain within thephysical proximity of other devices (e.g., mobile device 102 and mobilesensory device 114-1).

In an embodiment, the at least one feedback provided by the ARED 106 mayinclude visual feedback in the form of light emitted in one or morepatterns from the one or more light-emitting diodes (LED) and/or organiclight-emitting diodes (OLED) mounted on the housing or surface of theARED 106. In an embodiment, the at least one feedback provided by theARED 106 may also include audio feedback in the form series of acoustictones (e.g., square wave, sinusoidal wave, saw tooth wave, etc.) at aspecific frequency (e.g., 10 kHz, 15 kHz, etc.) with specific volume(e.g., ten (10) decibels, twenty (20) decibels, etc.), with a specificduration (e.g., one (1) second, two (2) seconds, etc.).

Additionally or alternatively, the audio feedback provided by ARED 106may further include voice feedback. In an embodiment, the voice feedbackmay notify the user in a specific language (e.g., English, French,German, etc.) with specific volume (e.g., ten (10) decibels, twenty (20)decibels, etc.) that a mobile sensory device (e.g., mobile sensorydevice 114-2) is not or may not remain in the physical proximity of theother devices in the same tethered segment (e.g., mobile device 102 andmobile sensory device 114-2 of tethered segment 118-1). The voicefeedback may also identify the specific device (e.g., identify mobilesensory device 114-2 as “a Utility Object of John Doe”) that is not orwill not remain in the physical proximity of the other devices.

FIGS. 7A and 7B illustrate example process operations performed by amobile device to actively track physical proximity of different devicesof a tethered segment. In various embodiments of FIGS. 7A and 7B, themobile device, which may be a designated lead device, may perform activetracking operations to determine and/or predict whether one or moredevices within a tethered segment are within physical proximity of thedesignated lead device or will remain within or leave the physicalproximity of the designated lead device according to exampleembodiments.

In the various embodiments of FIGS. 7A and 7B, the mobile device 102,the mobile sensory device 114-1, and the mobile sensory device 114-2 mayall be within the same tethered segment 118-1 and each of the mobilesensory devices may be within the predefined area 750 of mobile device102 to facilitate wireless communications with the mobile device 102either directly or indirectly over a local area network associated withthe mobile device 102. In various embodiments of FIGS. 7A and 7B, thepredefined area 750 may be representative of a limited or fixedgeographical region surrounding the mobile device 102 where each of themobile sensory devices in the tethered segment 118-1 may communicateeither directly or indirectly over the local area network associatedwith the mobile device 102. Additionally and in various embodiments ofFIGS. 7A and 7B, the mobile device 102 may be designated as a leaddevice and the mobile sensory devices 114-1 and 114-2 may be designatedas follower devices. In various embodiments of FIGS. 7A and 7B, themobile device 102 and the mobile sensory device 114-1 may begin to moveas illustrated at stages 752-1 and 752-2 while the mobile sensory 114-2may remain stationary.

In an embodiment and to determine whether devices in the tetheredsegment 118-1 are within the predefined area 750 of the mobile device102, the mobile device 102 may be configured to poll the one or morefollower devices via wireless connections and/or protocols in the localarea network associated with the mobile device 102. In an embodiment,the mobile device 102 may determine whether the mobile sensory devices114-1 and 114-2 are within predefined area 750 of the mobile device 102,when the mobile device 102 may communicate with each device in thetethered segment 118-1 via one or more wireless connections and/orprotocols on the local area network.

In an embodiment, the mobile device 102 may determine that the one ormore devices such as the mobile sensory device 114-1 and/or mobilesensory device 114-2 may not be within physical proximity of the mobiledevice 102, when the mobile device 102 is unable to ping or otherwiseunable to communicate with the one or more devices within a specificcommunication timeout period (e.g., five hundred (500) milliseconds, one(1) second, two (2) seconds, ten (10) seconds, etc.) In response to thatdetermination, the mobile device 102 may transmit one or more alertnotifications to the one or more devices within the tethered segment118-1 to indicate that the one or more devices are not within thetethered segment 118-1. Additionally or alternatively, the mobile device102 itself may provide at least one feedback to the user to indicatethat the one or more devices are not currently within the tetheredsegment 118-1.

Alternatively and as illustrated in FIG. 7A at stages 710-1 and 710-2,the mobile device 102 may determine that the mobile device 102 maycommunicate with the one or more devices such as the mobile sensorydevice 114-1 and mobile sensory device 114-2 within the tethered segment118-1. Assuming that the mobile device 102 may communicate with each ofthe devices in tethered segment 118-1, at stages 710-1 and 710-2 themobile device 102 may also optionally request and receive deviceconfiguration information from each device within the tethered segment118-1. In response to receiving the device configuration information forone or more devices, the mobile device 102 may also optionally updatethe device configuration information of the one or more devices storedin the device datastore 250. While not explicitly illustrated, it is tobe appreciated that the one or more stages (e.g., stages 710-1 and710-2) may be performed substantially simultaneously orcontemporaneously between the mobile device 102 and various deviceswithin the tethered segment 118-1. Additionally or alternatively, theone or more stages (e.g., stages 710-1 and 710-2) may also be performedin any order.

In an embodiment and to predict whether each of the devices within thetethered segment 118-1 will remain within the tethered segment 118-1when the one or more devices in the tethered segment 118-1 moves, themobile device 102 may determine whether all devices in the tetheredsegment 118-1 are moving substantially at the same time and/orsubstantially in the same direction. In an embodiment and at stage712-1, the mobile sensory device 114-1 may transmit its device activityinformation to the mobile device 102, when the mobile sensory device114-1 begins to move as indicated at stage 752-1. When this mobilesensory device 114-1 begins to move, the device may transition from anon-motion state (e.g., not moving) to a motion state (e.g., moving)after detecting motion and/or acceleration by its activity component(e.g., activity component 316 as illustrated in FIG. 3).

In an embodiment at stage 712-1, the mobile device 102 may also receivethe device configuration information transmitted from the mobile sensorydevice 114-1. In response, the mobile device 102 may also update thedevice configuration information of the mobile sensory device 114-1stored in the device datastore 450. Additionally and in response todetecting movement (e.g., detecting movement 752-2 of the mobile device102), the mobile device 102 may also update its device activityinformation stored in the device datastore 250.

In an embodiment, the mobile device 102 may wait for a specific updatetimeout period (e.g., two hundred fifty milliseconds (250), five hundred(500) milliseconds, one (1) second, etc.) after receiving deviceconfiguration information from the mobile sensory device 114-1 in orderto provide sufficient time for the mobile device 102 to receive deviceactivity information generated and/or transmitted from the mobilesensory device 114-2.

Additionally at stage 712-2 and optionally and after waiting for thespecific update timeout period, the mobile device 102 may optionallyrequest the device configuration information from mobile sensory device114-2. Additionally at stage 712-2, the mobile device 102 may optionallyfurther wait for another specific communication timeout period toreceive the device configuration information to be generated and/ortransmitted from the mobile sensory device 114-2.

In an embodiment, and after waiting for one or more timeout periodsdiscussed above, the mobile device 102 may begin to determine whetherall devices within the tethered segment 118-1 are moving substantiallyat the same time and/or substantially in the same direction. In anembodiment and to determine whether each of the mobile device 102,mobile sensory device 114-1, and mobile sensory device 114-2 are movingtogether substantially at the same time and/or substantially in the samedirection, the mobile device 102 may compare the past cumulative andmost recent in time device activity information (e.g., past five (5)seconds starting with the most recent in time device activityinformation) of mobile device 102, mobile sensory device 114-1, andmobile sensory device 114-2.

For example, the mobile device 102 may compare the past cumulative andmost recent in time device activity information of the mobile device102, which may be the designated lead device, with the past cumulativeand most recent in time device activity information of the one or moremobile sensory devices such as mobile sensory devices 114-1 and 114-2.Continuing with the example and in particular, the mobile device 102 maycompare at least the location information, motion state, and/or motiondirection of the mobile device 102 with respect to the mobile sensorydevices 114-1 and 114-2 to determine whether the mobile device 102,mobile sensory device 114-1, and mobile sensory device 114-2 are movingtogether.

In an embodiment and based on the comparison of device activityinformation of mobile device 102 and mobile sensory device 114-1, themobile device 102 may determine that the mobile device 102 is in asubstantially similar location, moving substantially at the same time,and/or moving substantially in the same direction as the mobile sensorydevice 114-1. As such, the mobile device 102 may predict that mobiledevice 102 and mobile sensory devices 114-1 may remain within physicalproximity of each other for a specific period of time (e.g., five (5)seconds, ten (10) seconds, thirty (30) seconds, sixty (60) seconds,etc.). However, based on the comparison of device activity informationof the mobile device 102 and mobile sensory device 114-2, the mobiledevice 102 may predict that the mobile device 102 and mobile sensorydevice 114-2 may not remain within physical proximity of each otherbecause they are not moving substantially at the same time or movingsubstantially in the same direction with respect to each other.

In an embodiment and after predicting that one or more devices (e.g.,mobile sensory device 114-2) within the tethered segment 118-1 may notremain within physical proximity of each other, then at stages 714-1 and714-2, the mobile device 102 may transmit one or more alertnotifications to the one or more devices in the tethered segment 118-1.In some embodiments, the mobile device 102, like the ARED 106 discussedin FIGS. 6A and 6B, may transmit one or more alert notifications to theonly the moving devices or only the non-moving (e.g., stationary)devices.

Additionally, the mobile device 102 itself may also provide at least onefeedback to the user. The at least one feedback provided by mobiledevice 102 may notify the user near the physical proximity of the mobiledevice 102 that the mobile sensory device 114-2 in tethered segment118-1 may not remain within physical proximity with mobile device 102and mobile sensory device 114-1.

In an embodiment, the at least one feedback provided by the mobiledevice 102 may include visual feedback in the form alert messages (e.g.,alert messages in the form of an email, mobile text, dialog box,notifications, etc.) that may be displayed on the display device of themobile device 102. In an embodiment, the at least one feedback providedby the mobile device 102 may also include audio feedback in the formseries of acoustic tones (e.g., square wave, sinusoidal wave, saw toothwave, etc.) at a specific frequency (e.g., 10 kHz, 15 kHz, etc.) withspecific volume (e.g., ten (10) decibels, twenty (20) decibels, etc.),with a specific duration (e.g., one (1) second, two (2) seconds, etc.).

Additionally or alternatively, the audio feedback provided by the mobiledevice 102 may further include voice feedback. In an embodiment, thevoice feedback may notify the user in a specific language (e.g.,English, French, German, etc.) with specific volume (e.g., ten (10)decibels, twenty (20) decibels, etc.) that a mobile sensory device(e.g., mobile sensory device 114-2) is not or will not remain in thephysical proximity of other devices in the same tethered segment (e.g.,mobile device 102 and mobile sensory device 114-2 of tethered segment118-1). The voice feedback may also identify the specific device (e.g.,identify mobile sensory device 114-2 as “a Utility Object of John Doe”)that is not or will not remain in the physical proximity of the otherdevices.

FIG. 8A illustrates example passive tracking operations that may beperformed by a mobile device and/or a mobile sensory device when themobile device and/or the mobile sensory device detects movement. It isto be appreciated that the mobile device and/or the mobile sensorydevice may perform the stages of FIG. 8A substantially in parallel orsimultaneously with respect to some or all stages further disclosed withrespect to FIGS. 8B and 8C.

At stage 810, the activity component (e.g. activity component 216 and/or316) of a mobile device and/or mobile sensory device (e.g., mobiledevice 102 and/or mobile sensory device 114-1) may generate deviceactivity information based on detected movement of a mobile deviceand/or a mobile sensory device. At stage 812, the activity component(e.g. activity component 216 and/or 316) of a mobile device and/ormobile sensory device (e.g., mobile device 102 and/or mobile sensorydevice 114-1) may store the device activity information of the mobiledevice and/or the mobile sensory device in a device datastore (e.g.,device datastore 250 and/or 450).

At stage 814, the management component (e.g., management component 214and/or 4314) of the mobile device and/or the mobile sensory device(e.g., mobile device 102 and/or mobile sensory device 114-1) maytransition one or more components (e.g., mobile processor component 284,embedded processor component 384, communications component 274,communications component 374, etc.) from a lower energy consumptionstate (e.g., a low-power state, etc.) to a higher energy consumptionstate (e.g., working state, etc.), in response to the detection ofmovement by the activity component. At stage 816, the managementcomponent (e.g., management component 214 and/or 314) of the mobiledevice and/or the mobile sensory device (e.g., mobile device 102 and/ormobile sensory device 114-1) may connect to an ARED or a mobile devicevia a local area network.

At stage 818, the management component (e.g., management component 214and/or 314) of the mobile device and/or the mobile sensory device (e.g.,mobile device 102 and/or mobile sensory device 114-1) may transmit thedevice activity information to an ARED or a mobile device via the localarea network. At stage 820, the management component (e.g., managementcomponent 214 and/or 414) of the mobile device and/or the mobile sensorydevice (e.g., mobile device 102 and/or mobile sensory device 114-1) maytransition the one or more components of the mobile device or the mobilesensory electronic device from their previous higher energy consumptionstate to the lower energy consumption state.

FIG. 8B illustrates example processing operations that may be performedby a mobile device and/or a mobile sensory device to receive at leastone alert notification from a mobile device and/or an ARED. It is to beappreciated that the mobile device and/or the mobile sensory device mayperform the stages of FIG. 8B substantially in parallel orsimultaneously with respect to some or all stages further disclosed withrespect to FIGS. 8A and 8C.

At stage 830 and assuming that no connection already exists to adesignated lead mobile device or an ARED, the management component(e.g., management component 214 and/or 314) of a mobile device and/or amobile sensory device (e.g., mobile device 102 and/or mobile sensorydevice 114-1) may optionally connect to a mobile device (e.g., adesignated lead mobile device) or an ARED via a local area network. Atstage 832, the management component (e.g., management component 214and/or 314) of a mobile device and/or a mobile sensory device (e.g.,mobile device 102 and/or mobile sensory device 114-1) may receive atleast one alert notification from the mobile device or the ARED.

At stage 834, the feedback component (e.g., feedback component 218and/or 318) of a mobile device and/or a mobile sensory device (e.g.,mobile device 102 and/or mobile sensory device 114-1) may activate atleast one feedback to indicate to a user that at least one device withina tethered segment is not within a predefined area (e.g., a predefinedarea of a designated lead mobile device 102 or an ARED 106) and/or ispredicted to not remain within the predefined area (e.g., the predefinedarea of a designated lead mobile device 102 or an ARED 106), in responseto receiving the at least one alert notification.

It is to be appreciated that in instances where a tethered segmentassociated with a user may include at least two mobile devices, afollower mobile device generally performing passive tracking operationsmay receive the at least one alert notification from a designated leadmobile device while the designed lead mobile device performing activetracking operations may transmit the at least one alert notification tothe follower mobile device so that the follower mobile device mayprovide appropriate feedback.

FIG. 8C illustrates example passive tracking operations that may beperformed by a mobile device and/or a mobile sensory device to receiveat least one device activity request for device activity informationfrom a different mobile device (e.g., follower mobile device) and/or anARED. It is to be appreciated that the mobile device and/or the mobilesensory device may perform the stages of FIG. 8C substantially inparallel or simultaneously with respect to some or all stages furtherdisclosed with respect to FIGS. 8A and 8B.

At stage 850 and assuming that no connection already exists to adesignated lead mobile device or an ARED, the management component(e.g., management component 214 and/or 314) of a mobile device and/or amobile sensory device (e.g., mobile device 102 and/or mobile sensorydevice 114-1) may optionally connect to a mobile device (e.g., adesignated lead mobile device) or an ARED via a local area network. Atstage 852, the management component (e.g., management component 214and/or 314) of a mobile device and/or a mobile sensory device (e.g.,mobile device 102 and/or mobile sensory device 114-1) may receive adevice activity request to retrieve device activity information.

At stage 854, the management component (e.g., management component 214and/or 314) of a mobile device and/or a mobile sensory device (e.g.,mobile device 102 and/or mobile sensory device 114-1) may retrieve thedevice activity information from the device datastore (e.g., devicedatastore 250 and/or 350). It is to be appreciated that the retrieveddevice activity information may include, without limitation, cumulativedevice activity information that includes the device activityinformation for a past specific period of time (e.g., past five (5)seconds) up to and including latest or most recent device activity whichmay be formatted as time series data.

At stage 856, the management component (e.g., management component 214and/or 314) may transmit the retrieved device activity information tothe requesting mobile device and/or ARED, in response to receiving thedevice activity request.

It is to be appreciated that in instances where a tethered segmentassociated with a user may include at least two mobile devices, afollower mobile device may receive a device activity request from adesignated lead mobile device while the designed lead mobile device maytransmit the device activity request to the follower mobile device sothat the follower mobile device may provide the device activityinformation.

FIG. 9A illustrates example active tracking operations that may beperformed by a designated lead mobile device when leaving and/orentering the physical proximity of an ARED in a local area network. Itis to be appreciated that the designated lead mobile device may performthe stages of FIG. 9A substantially in parallel or simultaneously withrespect to some or all stages further disclosed with respect to FIGS.9B-9E.

At stage 910, the proximity component (e.g., proximity component 220) ofa designated lead mobile device may determine that the designated leadmobile device (e.g., mobile device 102) is leaving and/or entering apredefined area of an ARED (e.g., ARED 106). For example, the designatedlead mobile device may determine that it is entering the predefined areaof the ARED 106, when the designated lead mobile device may wirelesslycommunicate with the ARED 106 via a local area network in a limitedgeographical area surrounding the ARED 106. Alternatively, thedesignated lead mobile device may determine that it is leaving thephysical proximity of the ARED 106, when the designated lead mobiledevice may no longer wirelessly communicate with the ARED 106 via thelocal area network in a limited geographical area surrounding the ARED106.

At stage 912, the proximity component (e.g., proximity component 220) ofthe designated lead mobile device may determine whether all otherdevices (e.g., mobile sensory device 114-1, mobile sensory device 114-2)of a tethered segment (e.g., tether segment 118-1) associated with thedesignated lead mobile device are within a predefined area of thedesignated lead mobile device (e.g., mobile device 102).

At stage 914 (illustrated as “Yes”), when the proximity component (e.g.,proximity component 220) of a designated lead mobile device (e.g.,mobile device 102) determines that all other devices (e.g., mobilesensory device 114-1 and mobile sensory device 114-2) are within thepredefined area of the designated lead mobile device, the process mayproceed to stage 919. This may indicate that the user who is inpossession of their designated lead mobile device also has possession oris at least within physical proximity of all other devices within thetethered segment when entering or exiting the physical proximity of theARED (e.g., ARED 106).

Alternatively at stage 914 (illustrated as “No”), when the proximitycomponent (e.g., proximity component 220) of a designated lead mobiledevice (e.g., mobile device 102) determines that at least one otherdevice (e.g., mobile sensory device 114-2) is not within predefined areaof the designated lead mobile device (e.g., mobile device 102), then theprocess may proceed to stage 916.

At stage 916, the management component (e.g., management component 214)of a designated lead mobile device (e.g., mobile device 102) maytransmit an alert notification to at least one other device (e.g.,mobile sensory device 114-2) within the tethered segment (e.g., tethersegment 118-1) to provide at least one feedback to the user.

Additionally in some implementations, the transmission of the alertnotification to the at least one other device may be periodic (e.g.,every one (1) second, every two (2) seconds, etc.) and/or continuous(e.g., continuously transmit for five (5) minutes for every two (2)seconds, etc.) to ensure that the at least one other device, which isnot within the predefined area of the designated lead mobile deviceand/or may be out of communications range, receives at least one alertnotification as soon as the designated lead mobile device moves withincommunication range. It is to be appreciated that by transmitting thealert notification to that at least one other device that is not withinphysical proximity and out of communication range of the designated leadmobile device, the user may easily locate the at least one other devicethat is not within the user's physical possession.

At stage 918, the feedback component (e.g., feedback component 218) of adesignated lead mobile device (e.g., mobile device 102) may activate atleast one feedback to provide at least one feedback to the user. The atleast one feedback may further indicate to the user regarding the atleast one other device that is not within the predefined area of thedesignated lead mobile device (e.g., mobile device 102).

At stage 919, the management component (e.g., the management component214) of a designated lead mobile device (e.g., mobile device 102) maytransition to either passive tracking operations or active trackingoperations based on whether the designated lead mobile device isentering or leaving the physical proximity of the ARED. For example, themanagement component 214 may transition the designated lead mobiledevice 102 to perform passive tracking operations when entering physicalproximity of the ARED 106 so that the ARED may begin to perform activetracking operations instead of the designated lead mobile device.

Alternatively, the management component 214 may transition thedesignated lead mobile device 102 to perform active tracking operationswhen leaving physical proximity of the ARED 106 so that the designatedlead mobile device may begin to perform active tracking operationsinstead of the ARED 106.

FIG. 9B illustrates example active tracking operations that may beperformed by a designated lead mobile device or an ARED to determinewhether a device is within a predefined area, which may be a limitedgeographical area surrounding the designated lead mobile device or theARED. In some implementations, a designated lead mobile device or anARED may perform the stages of FIG. 9B substantially in parallel orsimultaneously with respect to some or all stages further disclosed withrespect to FIGS. 9A and 9C-9E. In other implementations and upondetecting movement with respect to at least one device of a tetheredsegment, a designated lead mobile device or an ARED may perform thestages of FIG. 9B.

At stage 920, the proximity component (e.g., proximity component 220and/or 420) of a designated lead mobile device (e.g., mobile device 102)or an ARED (e.g., ARED 106) may determine whether all mobile devicesand/or mobile sensory devices of at least one tethered segment tetheredsegment (e.g., tethered segment 118-1, 118-2, etc.) is within thedesignated lead mobile device's or the ARED's predefined area.

At stage 922 (illustrated as “Yes”) and with respect to the designatedlead mobile device, when the proximity component (e.g., proximitycomponent 220) of the designated lead mobile device (e.g., mobile device102) determines that all other devices (e.g., mobile sensory device114-1, mobile sensory device 114-2) of a particular tethered segment(e.g., tethered segment 118-1) are within a predefined area of themobile device (e.g., mobile device 102), and therefore, withinsubstantial physical proximity with respect to all other devices, theprocess may end.

Similarly at stage 922 (illustrated as “Yes”) and with respect to anARED and for each tethered segment, when the proximity component (e.g.,proximity component 420) of the ARED (e.g., ARED 106) determines thatall devices (e.g., mobile device 102, mobile sensory device 114-1, andmobile sensory device 114-2) of a particular tethered segment (e.g.,tethered segment 118-1) are within predefined area of the ARED (e.g.,ARED 106) and therefore, within substantial physical proximity withrespect to each other, the process may end.

It is to be appreciated that the determinations by the proximitycomponents discussed above may indicate that all devices (e.g., mobiledevice 102, mobile sensory device 114-1, mobile sensory device 114-2) ofa tethered segment (e.g., tethered segment 118-1) associated with a userare either within physical proximity of the designated lead mobiledevice (e.g., mobile device 102) or the ARED (e.g., ARED 106). Thus, noalert notifications should be given at this time and the process mayend.

Alternatively at stage 922 (illustrated as “No”) and with respect to adesignated lead mobile device (e.g., mobile device 102), when theproximity component (e.g., proximity component 220) of the designatedlead mobile device (e.g., mobile device 102) determines that at leastone other device (e.g., mobile sensory device 114-2) is not within thepredefined area of the designated lead mobile device (e.g., mobiledevice 102), then the process may proceed to stage 924.

Similarly at stage 922 (illustrated as “No”) and with respect to an AREDand for each tethered segment, when the proximity component (e.g.,proximity component 420) of the ARED (e.g., ARED 106) determines that:(1) at least one device (e.g., mobile sensory device 114-2) of aparticular tethered segment (e.g., tethered segment 118-1) is not withinthe predefined area of the ARED (e.g., ARED 106); and (2) at least oneother device (e.g., mobile device 102) of the same particular tetheredsegment is within the predefined area of the ARED (e.g., ARED 106), thenthe process may also proceed to stage 924.

It is to be appreciated that the determinations by the proximitycomponent 220 of the designated lead mobile device at stage 922(illustrated as “No”), may indicate that at least one device (e.g.,mobile sensory device 114-2) of a tethered segment (e.g., tetheredsegment 118-1) associated with a user is not within the physicalproximity of the designated lead mobile device (e.g., mobile device102). Similarly, the determinations by the proximity component 420 ofthe ARED at stage 922 (illustrated as “No”) may indicate that at leastone device (e.g., mobile sensory device 114-2) of a tethered segment isnot within the physical proximity of the ARED while at least one otherdevice (e.g., mobile device 102) is within the physical proximity of theARED. Thus, these determinations may indicate that a user has forgottenor left behind a utility object and an alert notification should beprovided.

At stage 924, the management component (e.g., management component 214and/or 414) of the designated lead mobile device (e.g., mobile device102) or the ARED (e.g., ARED 106) may transmit an alert notification toat least one other device (e.g., mobile sensory device 114-2) within thetethered segment (e.g., tethered segment 118-1) to provide at least onefeedback to the user.

Additionally in some implementations, the transmission of the alertnotification from a designated lead mobile device to the at least oneother device may be periodic (e.g., every one (1) second, every two (2)seconds, etc.) and/or continuous (e.g., continuously transmit for five(5) minutes for every two (2) seconds, etc.) to ensure that the at leastone other device, which may be out of communications range, receives atleast one alert notification as soon as the designated lead mobiledevice moves within communication range. It is to be appreciated that bytransmitting the alert notification to that at least one other devicethat is not within physical proximity and out of communication range ofthe designated lead mobile device, the user may easily locate the atleast one other device that is not within the user's physicalpossession.

At stage 926, the feedback component (e.g., feedback component 218and/or 418) of the designated lead mobile device (e.g., mobile device102) or the ARED (e.g., ARED 106) may activate at least one feedback toprovide at least one feedback to the user. The at least one feedback mayfurther indicate to the user regarding a particular device (e.g., mobilesensory device 114-2) of a tethered segment (e.g., tethered segment118-1) that was determined to be not within the physical proximity ofthe designated lead mobile device (e.g., mobile device 102) or the ARED(e.g., ARED 106).

FIG. 9C illustrates example active tracking operations that may beperformed by a designated lead mobile device or an ARED to receive andupdate device activity information received from a follower device. Insome implementations, a designated lead mobile device or an ARED mayperform the stages of FIG. 9C substantially in parallel orsimultaneously with respect to some or all stages further disclosed withrespect to FIGS. 9A, 9B, 9D, and 9E.

At stage 930, a management component (e.g., management component 214and/or 414) of a designated lead mobile device (e.g., mobile device 102)or an ARED (e.g., ARED 106) may be may receive device activityinformation via a local area network from at least one follower mobiledevice or mobile sensory device (e.g., mobile sensory device 114-1,114-2, etc.), wherein the device activity information includes at leasta device identifier (e.g., device identifier “Device_ID_2” thatidentifies mobile sensory device 114-1, etc.), motion state(s), motiondirection(s), and update time stamp(s) for the device that transmittedthe device activity information.

At stage 932, the management component (e.g., management component 214and/or 414) of the designated lead mobile device (e.g., mobile device102) or the ARED (ARED 106), may update device activity informationstored in the device datastore (e.g., device datastore 250 and/or 450)based on the device activity information received from the least onemobile device and/or mobile sensory device.

It is to be appreciated that by repeatedly performing the operations inat least FIGS. 9A-9C and FIGS. 8A-8C in real-time or substantially nearreal-time in cooperation with each other as discussed, the mobilesensory system 100 may at least quickly determine whether any deviceswithin a particular tethered segment may be inside or outside thelimited geographical area surrounding a designated lead mobile device orARED.

FIG. 9D illustrates example active tracking operations that may beperformed by a designated lead mobile device or an ARED to predictwhether all devices of a tether segment that is moving will remainwithin or leave physical proximity of each other.

At stage 950, a proximity component (e.g., proximity component 220and/or 420) of a designated lead mobile device (e.g., mobile device 102)and/or ARED (e.g., ARED 106) may determine whether all devices within atethered segment (e.g., tethered segment 118-1) associated with a userare currently moving. At stage 952 (illustrated as “Yes”), when theproximity component determines that all devices (e.g., mobile device102, mobile sensory device 114-1, mobile sensory device 114-2) within atethered segment (e.g., tethered segment 118-1) are moving, then theprocess may proceed to stage 954. Alternatively at stage 952(illustrated as “No”), when the proximity component determines that atleast one device (e.g., mobile sensory device 1104), within the tetheredsegment (e.g., tethered segment 118-1) is not moving, then the processmay proceed to stage 970 of FIG. 9E.

At stage 954, the proximity component (e.g., proximity component 220and/or 420) of the designated lead mobile device (e.g., mobile device102) and/or the ARED (e.g., ARED 106) may determine whether all devicescurrently moving within the tethered segment also started moving atsubstantially same time and/or substantially same direction. Forexample, the proximity component may determine that all devices startedmoving at substantially the same time when the maximum time differencebetween a first device to transition from a non-moving state to a movingstate (i.e., started moving) and a last device to transition from anon-moving state to a moving state (i.e., started moving) does notexceed a specific period of time (e.g., 500 milliseconds, one (1)second, etc.). Additionally, the proximity component may determine thatall devices started moving at substantially same direction when themotion directions of all devices are substantially equal (e.g., alldevices are moving West, etc.)

At stage 956 (illustrated as “Yes”), when proximity component (e.g.,proximity component 220 and/or 420) of the designated lead mobile device(e.g., mobile device 102) and/or the ARED (e.g., ARED 106) determinesthat all devices started moving at substantially same time and/or samedirection within the tethered segment (e.g., tethered segment 118-1),then the process may proceed to stage 958. Alternatively at stage 956(illustrated as “No”), when the proximity component determines that atleast one device (e.g., mobile sensory device 1104), within the tetheredsegment (e.g., tethered segment 118-1) is not moving at substantiallysame time or same direction within the tethered segment (e.g., tetheredsegment 118-1), then the process may proceed to stage 972 of FIG. 9E.

At stage 958, the proximity component (e.g., proximity component 220and/or 420) of the designated lead mobile device (e.g., mobile device102) and/or the ARED (e.g., ARED 106) may determine whether all devicescurrently moving within the tethered segment have been moving for aminimum continuous movement period. For example and for each device(e.g., mobile device 102, mobile sensory device 114-1, mobile sensorydevice 114-2) of a tethered segment (e.g., tethered segment 118-1), theproximity component may determine whether each device has been movingfor a minimum continuous movement period. Continuing with the example,the proximity component may determine that a device has been moving fora minimum continuous movement period, when the device that is currentlymoving within the tethered segment has remained or persisted in themoving state for the minimum continuous movement period (e.g., two (2)seconds, three (3) seconds, etc.).

At stage 960 (illustrated as “No”), when proximity component (e.g.,proximity component 220 and/or 420) of the designated lead mobile device(e.g., mobile device 102) and/or the ARED (e.g., ARED 106) determinesthat at least one device has not been moving for a minimum continuousmovement period, then the process may proceed to stage 962.Alternatively at stage 960 (illustrated as “Yes”), when the proximitycomponent determines that all devices (e.g., mobile device 102, mobilesensory device 114-1, mobile sensory device 114-2) within the tetheredsegment (e.g., tethered segment 118-1) has been moving together for aminimum continuous movement period then the process may end, which mayindicate that the user associated with the tethered segment haspossession of utility objects and devices he is keeping track of becauseall objects and devices are moving together with the user.

At stage 962, the proximity component (e.g., proximity component 220and/or 420) of the designated lead mobile device (e.g., mobile device102) and/or the ARED (e.g., ARED 106) may wait for the minimumcontinuous movement period before proceeding back to stage 950.

FIG. 9E illustrates additional example active tracking operations thatmay be performed by a designated lead mobile device or an ARED topredict whether a mobile device or a mobile sensory device of a tetheredsegment that is moving will remain within or leave physical proximity ofeach other.

At stage 970 (illustrated as “Yes”) and after performing stage 952 atFIG. 9D, the proximity component (e.g., proximity component 220 and/or420) of the designated lead mobile device (e.g., mobile device 102)and/or the ARED (e.g., ARED 106) may proceed to stage 972, when theproximity component determines that at least one device is moving, i.e.,in a motion state. Alternatively at stage 972 (illustrated as “No”), theprocess may end which may indicate that there are no devices within thetethered segment that are currently moving, i.e., all devices within thetethered segment have remained stationary, i.e., in a not moving state.

At stage 972, the proximity component (e.g., proximity component 220and/or 420) of the designated lead mobile device (e.g., mobile device102) and/or the ARED (e.g., ARED 106) may determine whether each devicewithin the tethered segment that is moving also moved for a minimumcontinuous movement period. For example and for each device (e.g.,mobile device 102, mobile sensory device 114-1, mobile sensory device114-2) within the tethered segment (e.g., tethered segment 118-1) thatis currently moving, the proximity component may determine whether eachdevice has been moving for a minimum continuous movement period.

At stage 974 (illustrated as “Yes”), when the proximity component (e.g.,proximity component 220 and/or 420) of the designated lead mobile device(e.g., mobile device 102) and/or the ARED (e.g., ARED 106) determinesthat all the devices that are currently moving have been for a minimumcontinuous movement period, then the process may proceed to stage 976.Alternatively at stage 974 (illustrated as “No”), the process mayproceed to stage 984, where the proximity component (e.g., proximitycomponent 220 and/or 420) of the designated lead mobile device (e.g.,mobile device 102 may wait for the minimum continuous movement periodbefore proceeding back to stage 950 of FIG. 9D.

At stage 976, the proximity component (e.g., proximity component 220and/or 420) of the designated lead mobile device (e.g., mobile device102) and/or the ARED (e.g., ARED 106) may determine whether eachnon-moving device within the tethered segment has not moved for aminimum non-movement period. For example and for each device (e.g.,mobile device 102, mobile sensory device 114-1, mobile sensory device114-2) within the tethered segment (e.g., tethered segment 118-1) thatis not currently moving, the proximity component may determine whethereach device has not been moving for a minimum continuous non-movementperiod. Continuing with the example, the proximity component maydetermine that a device has not been moving for a minimum continuousnon-movement period, when the device that is currently not moving, i.e.,stationary within the tethered segment has remained or persisted in thenot moving state for the minimum continuous non-movement period (e.g.,two (2) seconds, three (3) seconds, etc.).

At stage 978 (illustrated as “Yes”), when the proximity component (e.g.,proximity component 220 and/or 420) of the designated lead mobile device(e.g., mobile device 102) and/or the ARED (e.g., ARED 106) determinesthat all the devices that are currently not moving have remainedstationary for a minimum continuous non-movement period, then theprocess may proceed to stage 980. Alternatively, at stage 978(illustrated as “No”), the process may proceed to stage 986, where theproximity component of the designated lead mobile device (e.g., mobiledevice 102) and/or the ARED (e.g., ARED 106) may wait for the minimumcontinuous non-movement period before proceeding back to stage 950 ofFIG. 9D.

It is to be appreciated that by waiting for the minimum continuousmovement period at one or more stages (e.g., stages 962 and 984), theproximity component may reduce potential false positives that may occurwhen a device (e.g., mobile device 102, mobile sensory device 114-1,etc.) within the tethered segment (e.g., tethered segment 118-1) beginsto move merely because the user has picked up the device (e.g., mobiledevice 102) for a nominal period of time for purposes of examination,manipulation, or minor relocation.

Similarly, by waiting for a minimum continuous non-movement period atleast one stage (e.g., stage 986), the proximity component may reducepotential false positives that may occur when a device (e.g., mobiledevice 102, mobile sensory device 114-1, etc.) within the tetheredsegment (e.g., tethered segment 118-1) is momentarily put down by theuser and thus remains stationary for a nominal period of time but isthen picked back up again for further relocation.

Additionally, it is to be appreciated that such wait periods (e.g.,minimum continuous movement period at stages 962 and 984 and minimumcontinuous non-movement period stage 986) may also reduce potentialfalse positives that may arise due to nominal variances and/orinaccuracies in motion detection by the activity component 216 andactivity component 316 via various components of the mobile deviceand/or mobile sensory device.

At stage 980, the management component (e.g., management component 214and/or 414) of the designated lead mobile device (e.g., mobile device102) or ARED (e.g., ARED 106) may generally transmit an alertnotification to at least one device (e.g., mobile sensory device 114-2)within the tethered segment (e.g., tethered segment 118-1) to provide atleast one feedback to the user indicating that the at least one deviceis predicted to not remain within physical proximity of the designatedlead mobile device or ARED.

Additionally at stage 980, in instances when the ARED is performing theprocesses discussed in FIGS. 9D and 9E, the management component of theARED may transmit the alert notification to at least the designated leadmobile device. Furthermore and at stage 980, in instances when thedesigned lead mobile device is performing active tracking operationsdiscussed in FIGS. 9D and 9E, the management component of the designedlead mobile device may optionally transmit the alert notification to atleast one device that has a motion state opposite of the designed leadmobile device. For example, if the designated lead mobile device withinthe tether segment is currently in a moving state, then the designatedlead mobile device may transmit an alert notification to any devicesthat is not in a moving state within the same tethered segment and viceversa.

At stage 982, the feedback component (e.g., feedback component 218and/or 418) of a designated lead mobile device (e.g., mobile device 102)and/or ARED (e.g., ARED 106) may activate at least one feedback toprovide at least one feedback to the user indicating that at least onedevice within the tethered segment (e.g., tethered segment 118-1) thatis predicted to not remain within the physical proximity of thedesignated lead mobile device or ARED. The at least one feedback mayfurther indicate to the user regarding which particular device (e.g.,mobile sensory device 114-2) within the tethered segment (e.g., tetheredsegment 118-1) that is predicted to not remain within the physicalproximity of the designated lead mobile device (e.g., mobile device 102)or ARED (e.g., ARED 106).

It is to be appreciated that by repeatedly performing the operations inat least FIGS. 8A-8C and FIGS. 9C-9E in real-time or substantially nearreal-time in cooperation with each other as discussed, the mobilesensory system 100 may quickly predict whether any devices within aparticular tethered segment may remain within the limited geographicalarea surrounding a designated lead mobile device or ARED.

It is to be further appreciated that while some of the above exampleembodiments illustrated in FIGS. 1-4, 5A-5C, 6A-6B, 7A-7B, 8A-8C and9A-9E may have been described in substantial detail with respect tomobile device 102, ARED 106, and mobile sensory devices 114-1 and 114-2,the example embodiments are not limited to those contexts and/ordevices.

Example Computer System

Various embodiments and components therein can be implemented, forexample, using one or more well-known computer systems, such as, forexample, the example embodiments, systems, and/or devices (e.g., mailservers, SMS servers, etc.) shown in the figures or otherwise discussed.Computer system 1000 can be any well-known computer capable ofperforming the functions described herein.

Computer system 1000 includes one or more processors (also calledcentral processing units, or CPUs), such as a processor 1004. Processor1004 is connected to a communication infrastructure or bus 1006.

One or more processors 1004 may each be a graphics processing unit(GPU). In an embodiment, a GPU is a processor that is a specializedelectronic circuit designed to process mathematically intensiveapplications. The GPU may have a parallel structure that is efficientfor parallel processing of large blocks of data, such as mathematicallyintensive data common to computer graphics applications, images, videos,etc.

Computer system 1000 also includes user input/output device(s) 1003,such as monitors, keyboards, pointing devices, etc., that communicatewith communication infrastructure 1006 through user input/outputinterface(s) 1002.

Computer system 1000 also includes a main or primary memory 1008, suchas random access memory (RAM). Main memory 1008 may include one or morelevels of cache. Main memory 1008 has stored therein control logic(i.e., computer software) and/or data.

Computer system 1000 may also include one or more secondary storagedevices or memory 1010. Secondary memory 1010 may include, for example,a hard disk drive 1012 and/or a removable storage device or drive 1014.Removable storage drive 1014 may be a floppy disk drive, a magnetic tapedrive, a compact disk drive, an optical storage device, tape backupdevice, and/or any other storage device/drive.

Removable storage drive 1014 may interact with a removable storage unit1018. Removable storage unit 1018 includes a computer usable or readablestorage device having stored thereon computer software (control logic)and/or data. Removable storage unit 1018 may be a floppy disk, magnetictape, compact disk, DVD, optical storage disk, and/any other computerdata storage device. Removable storage drive 1014 reads from and/orwrites to removable storage unit 1018 in a well-known manner.

According to an exemplary embodiment, secondary memory 1010 may includeother means, instrumentalities or other approaches for allowing computerprograms and/or other instructions and/or data to be accessed bycomputer system 1000. Such means, instrumentalities or other approachesmay include, for example, a removable storage unit 1022 and an interface1020. Examples of the removable storage unit 1022 and the interface 1020may include a program cartridge and cartridge interface (such as thatfound in video game devices), a removable memory chip (such as an EPROMor PROM) and associated socket, a memory stick and USB port, a memorycard and associated memory card slot, and/or any other removable storageunit and associated interface.

Computer system 1000 may further include a communication or networkinterface 1024. Communication interface 1024 enables computer system1000 to communicate and interact with any combination of remote devices,remote networks, remote entities, etc. (individually and collectivelyreferenced by reference number 1028). For example, communicationinterface 1024 may allow computer system 1000 to communicate with remotedevices 1028 over communications path 1026, which may be wired and/orwireless, and which may include any combination of LANs, WANs, theInternet, etc. Control logic and/or data may be transmitted to and fromcomputer system 1000 via communications path 1026.

In an embodiment, a non-transitory, tangible apparatus or article ofmanufacture comprising a non-transitory, tangible computer useable orreadable medium having control logic (software) stored thereon is alsoreferred to herein as a computer program product or program storagedevice. This includes, but is not limited to, computer system 1000, mainmemory 1008, secondary memory 1010, and removable storage units 1018 and1022, as well as tangible articles of manufacture embodying anycombination of the foregoing. Such control logic, when executed by oneor more data processing devices (such as computer system 1000), causessuch data processing devices to operate as described herein.

Based on the teachings contained in this disclosure, it will be apparentto persons skilled in the relevant art(s) how to make and useembodiments of this disclosure using data processing devices, computersystems and/or computer architectures other than that shown in FIG. 10.In particular, embodiments may operate with software, hardware, and/oroperating system implementations other than those described herein.

CONCLUSION

It is to be appreciated that the Detailed Description section, and notthe Summary and Abstract sections, is intended to be used to interpretthe claims. The Summary and Abstract sections can set forth one or morebut not all exemplary embodiments as contemplated by the inventor, andthus, are not intended to limit this disclosure or the appended claimsin any way.

While this disclosure describes exemplary embodiments for exemplaryfields and applications, it should be understood that the disclosure isnot limited thereto. Other embodiments and modifications thereto arepossible, and are within the scope and spirit of this disclosure. Forexample, and without limiting the generality of this paragraph,embodiments are not limited to the software, hardware, firmware, and/orentities illustrated in the figures and/or described herein. Further,embodiments (whether or not explicitly described herein) havesignificant utility to fields and applications beyond the examplesdescribed herein.

Embodiments have been described herein with the aid of functionalbuilding blocks illustrating the implementation of specified functionsand relationships thereof. The boundaries of these functional buildingblocks have been arbitrarily defined herein for the convenience of thedescription. Alternate boundaries can be defined as long as thespecified functions and relationships (or equivalents thereof) areappropriately performed. Also, alternative embodiments can performfunctional blocks, steps, operations, methods, etc. using orderingsdifferent than those described herein.

References herein to “one embodiment,” “an embodiment,” “an exampleembodiment,” or similar phrases, indicate that the embodiment describedcan include a particular feature, structure, or characteristic, butevery embodiment can not necessarily include the particular feature,structure, or characteristic. Moreover, such phrases are not necessarilyreferring to the same embodiment. Further, when a particular feature,structure, or characteristic is described in connection with anembodiment, it would be within the knowledge of persons skilled in therelevant art(s) to incorporate such feature, structure, orcharacteristic into other embodiments whether or not explicitlymentioned or described herein. Additionally, some embodiments can bedescribed using the expression “coupled” and “connected” along withtheir derivatives. These terms are not necessarily intended as synonymsfor each other. For example, some embodiments can be described using theterms “connected” and/or “coupled” to indicate that two or more elementsare in direct physical or electrical contact with each other. The term“coupled,” however, can also mean that two or more elements are not indirect contact with each other, but yet still co-operate or interactwith each other.

The breadth and scope of this disclosure should not be limited by any ofthe above-described exemplary embodiments, but should be defined only inaccordance with the following claims and their equivalents.

What is claimed is:
 1. A tracking device, comprising: at least oneprocessor; and a memory operatively coupled to the at least oneprocessor, wherein the at least one processor is configured to:determine whether a first device and a second device are within apredefined area of the tracking device based at least on a determinationof whether the first device and the second device are able tocommunicate with the tracking device, predict whether the first devicewill move outside a physical proximity of the second device based atleast on a determination that the first device has moved for at least aminimum continuous movement period while the second device has not movedfor at least a minimum continuous non-movement period, and transmit atleast one alert notification to the first device or the second devicebased at least on a prediction that the first device will move outsidethe physical proximity of the second device.
 2. The tracking device ofclaim 1, wherein the at least one processor is further configured to:receive first device activity information from the first device andsecond device activity information from the second device, wherein thefirst device activity information includes a device identifier of thefirst device, a motion state of the first device, a motion direction ofthe first device, and/or an update time stamp of the first device, andthe second device activity information includes a device identifier ofthe second device, a motion state of the second device, a motiondirection of the second device, and/or an update time stamp of thesecond device.
 3. The tracking device of claim 2, wherein to predictwhether the first device will move outside the physical proximity of thesecond device, the at least one processor is further configured to:determine whether the first device is moving substantially at a sametime and/or substantially in a same direction as the second device basedat least on the first device activity information and the second deviceactivity information, and determine whether the first device has movedfor at least the minimum continuous movement period and the seconddevice has not moved for at least the minimum continuous non-movementperiod.
 4. The tracking device of claim 3, wherein the at least oneprocessor is further configured to: determine that the first device andthe second device are within the predefined area of the tracking device,when the first device is able to communicate with the tracking deviceutilizing a first wireless communications protocol, and the seconddevice is able to communicate with the tracking device utilizing asecond wireless communications protocol.
 5. The tracking device of claim2, wherein the tracking device is an audio responsive electronic device(ARED) and the at least one processor of the ARED is further configuredto: activate, by the ARED, at least one feedback based at leastpartially on the prediction that the first device will move outside thephysical proximity of the second device.
 6. The tracking device of claim5, wherein the at least one feedback of the ARED includes voice feedbackconfigured to notify a user in a specific language with a specificvolume that the first device is predicted to move outside the physicalproximity of the second device and/or visual feedback configured to emitone or more patterns from one or more light emitting diodes (LEDs)mounted on a housing of the ARED.
 7. The tracking device of claim 2,wherein the first device is a mobile device and the at least one alertnotification is an email message transmitted to an email addressassociated with a user of the mobile device, and the email messageidentifies the second device and indicates that the first device is notwithin the physical proximity of the second device.
 8. A computerimplemented method, comprising: determining, by a tracking device,whether a first device and a second device are within a predefined areaof the tracking device based at least on a determination of whether thefirst device and the second device are able to communicate with thetracking device; predicting, by the tracking device, whether the firstdevice will move outside a physical proximity of the second device basedat least on a determination that the first device has moved for at leasta minimum continuous movement period while the second device has notmoved for at least a minimum continuous non-movement period; andtransmitting, by the tracking device, at least one alert notification tothe first device or the second device based at least on a predictionthat the first device will move outside the physical proximity of thesecond device.
 9. The computer implemented method of claim 8, whereinthe predefined area is representative of a geographical regionsurrounding the tracking device, and the at least one alert notificationidentifies the first device and indicates that the first device ispredicted to move outside the physical proximity of the second device.10. The computer implemented method of claim 9, wherein the determiningof whether the first device and the second device are within thepredefined area of the tracking device further comprises: determiningthat the first device and the second device are within the predefinedarea of the tracking device, when the first device is able tocommunicate with the tracking device utilizing a first wirelesscommunications protocol and the second device is able to communicatewith the tracking device utilizing a second wireless communicationsprotocol.
 11. The computer implemented method of claim 9, furthercomprising: activating, by the tracking device, at least one feedbackbased at least partially on a indication that the first device ispredicted to move outside the physical proximity of the second device,wherein the at least one feedback includes voice feedback configured tonotify a user in a specific language with a specific volume that thefirst device is predicted to move outside the physical proximity of thesecond device.
 12. The computer implemented method of claim 8, whereinthe first device is a mobile device and the at least one alertnotification is a text message transmitted to a phone number associatedwith a user of the mobile device, and the text message identifies thesecond device and indicates that the first device is moving without thesecond device.
 13. The computer implemented method of claim 8, furthercomprising: receiving, by the tracking device, first device activityinformation from the first device, receiving, by the tracking device,second device activity information from the second device, and updating,by the tracking device, a device datastore configured to store the firstdevice activity information and the second device activity information.14. The computer implemented method of claim 13, wherein the predictingof whether the first device will move outside the physical proximity ofthe second device further comprises: determining, by the trackingdevice, that the first device has been moving for at least the minimumcontinuous movement period based at least on the first device activityinformation; and determining, by the tracking device, that the seconddevice has not been moving for at least the minimum continuousnon-movement period based at least on the second device activityinformation previously stored in the device datastore, wherein thedetermining that the first device has been moving and the second devicehas not been moving indicates that the first device is predicted to moveoutside the physical proximity of the second device.
 15. A tangiblecomputer-readable medium having instructions stored thereon that, whenexecuted by at least one computing device, causes the at least onecomputing device to perform operations comprising: determining whether afirst device and a second device are within a predefined area of atracking device based at least on a determination of whether the firstdevice and the second device are able to communicate with the trackingdevice; predicting whether the first device will move outside a physicalproximity of the second device based at least on a determination thatthe first device has moved for at least a minimum continuous movementperiod while the second device has not moved for at least a minimumcontinuous non-movement period; and transmitting at least one alertnotification to the first device or the second device based at least ona prediction that the first device will move outside the physicalproximity of the second device.
 16. The computer-readable medium ofclaim 15, wherein the operations further comprise: receiving firstdevice activity information from the first device and second deviceactivity information from the second device, wherein the first deviceactivity information includes a device identifier of the first device, amotion state of the first device, a motion direction of the firstdevice, and/or an update time stamp of the first device, and the seconddevice activity information includes a device identifier of the seconddevice, a motion state of the second device, a motion direction of thesecond device, and/or an update time stamp of the second device.
 17. Thecomputer-readable medium of claim 16, wherein the operation forpredicting whether the first device will move outside the physicalproximity of the second device further comprises: determining whetherthe first device is moving substantially at same time and/orsubstantially in same direction as the second device based at least onthe first device activity information and the second device activityinformation; and determining whether the first device has moved for atleast the minimum continuous movement period and the second device hasnot moved for at least the minimum continuous non-movement period. 18.The computer-readable medium of claim 17, wherein the operations furthercomprise: determining that the first device and the second device arewithin the predefined area of the tracking device, when the first deviceis able to communicate with the tracking device utilizing a firstwireless communications protocol and the second device is able tocommunicate with the tracking device utilizing a second wirelesscommunications protocol.
 19. The computer-readable medium of claim 18,wherein the operations further comprise: activating at least onefeedback based at least on the determination that the first device isoutside the predefined area while the second device is inside thepredefined area, wherein the at least one feedback includes voicefeedback configured to notify a user in a specific language with aspecific volume that the first device is not within the physicalproximity of the second device and/or visual feedback configured to emitone or more patterns from one or more light emitting diodes (LEDs)mounted on a housing of the tracking device.
 20. The computer-readablemedium of claim 16, wherein the first device is a mobile device and theat least one alert notification is an email message transmitted to anemail address associated with a user of the mobile device, and the emailmessage identifies the second device and indicates that the seconddevice is not within physical proximity of the first device.